Solved! Go to Solution.
The concept that you've outlined is not correct, from what I have read in:
Oh sorry, didn't see saying Copies. then yeah only Active Databases will be archived, not the copies etc
But anyho, based on that guide, if a DAG failover occurs and the users mailbox is now being archived by a task on another server, the following applies (which i mentioned originally)
"Yes, it is possible that performance would be affected. For example if you have a scenario where you have a 1:1 relationship of 1 Enterprise Vault server per Exchange Mailbox Server and with a DAG configuration similar to that of the customer scenario in this document, if MailboxDatabase1 fails over to MailboxServer2, once the provisioning task has run, the mailboxes in MailboxServer2 will now be processed by the second EV server as that is the server that hosts the archiving task for MailboxServer2. In addition to already archiving mailboxes in MailboxDatabase3 and MailboxDatabase4, the second EV server now has to process mailboxes in MailboxDatabase1 and MailboxDatabase2. In that event the Enterprise Vault server will have more mailboxes to process, and because the storage service associated with archives relating to mailboxes in MailboxDatabase1 and MailboxDatabase2 will reside on the first EV server, archived data will have to be transferred over MSMQ to the first EV server. "
I am new to EV so can you please explain me in more details "the storage service associated with archives relating to mailboxes in MailboxDatabase1 and MailboxDatabase2 will reside on the first EV server, archived data will have to be transferred over MSMQ to the first EV server. "
Since we will have 1:1 relationship of 1 EV server per Mailbox server, how should we map the storage drives on each EV servers, since as per my understanding storage drives on EV A will not be available on EV B server, I need to understand the process by which MSMQ will transfer the data to first EV server when the mailboxes are processed on second EV server.