cancel
Showing results for 
Search instead for 
Did you mean: 

Enterprise Vault Journaling with Exchange Server 2010 DAG

Using Enterprise Vault 11 with Exchange 2013

How do I create a Journaling Task so it will work with a DAG? e.g., Journaling mailbox is currently active on Serv1, I want to ensure EV is able to still pickup the journaled items when the mailbox becomes active on Serv2.

I've read http://www.symantec.com/business/support/index?page=content&id=TECH197848 but when creating a target I can only point to mailbox servers and not a DAG or CAS array.

 

Thanks

Chad

1 Solution

Accepted Solutions
Accepted Solution!

Actually provisioning isn't a

Actually provisioning isn't a hard requirement, it still works, it just slows down looking up Wher its moved to Sometimes provisioning can take an hour, so if you think you might roll back in two hours or less, it's not worth running provisioning for a few seconds of extra inconvenience to an end user
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

3 Replies

Simply create a task against

Simply create a task against the primary DAG server (or at least the active one now) where the Journal Mailbox exists, when the DAG failover occurs, the next time it attempts to connect, it will determine that a failover has occured and find the Mailbox on another exchange server

obviously you should test this

http://www.symantec.com/business/support/index?page=content&id=TECH197848

 

https://www.linkedin.com/in/alex-allen-turl-07370146

Currently, Enterprise Vault

Currently, Enterprise Vault still targets an Exchange server, not a DAG.

For Journal Archiving, I say: Journal Archiving follows mailbox. (like JW3 states above), Mailbox Archiving requires provisioning to follow mailboxes.

Regards. Gertjan
Accepted Solution!

Actually provisioning isn't a

Actually provisioning isn't a hard requirement, it still works, it just slows down looking up Wher its moved to Sometimes provisioning can take an hour, so if you think you might roll back in two hours or less, it's not worth running provisioning for a few seconds of extra inconvenience to an end user
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post