Hi,
We have one client who has 48 exchange DBs divided to Exchange 2013 DAG having 12 nodes. Each ExchDB has active and passive version so that if some problem occurrs the other node takes over the DB.
I have 2 EV server cluster to cover these 12 tasks, 6 each.
The behaviour that I'm seeing is that the automatic archiving is slow or nonexistent apparently due to the fact that when the A5 queue is loaded with the mboxes of that time it handles a portion. Then the scheluded time is over and task stops it work. If the DB now moves to another ExchNode the unhandled archive requests stays in A5 queue and when the next scheduled run starts it halts to wonder these queued requests that are no longer on that node that it's supposed to handle and the automatic archiving / mailbox synchronizing is extremely slow or nonexistent and the MSMQs just never seems to get done... Is there a solution for this behavior?
Found this forum discussion:
What is SyncinMirgationMode registry key mentioned in there?
Environmental facts:
Around 44 000 mailboxes - around 10 000 Enabled for EV
Exchange 2013 CF5
DAG 12 nodes
48 Exchange DB
Enterprise vault 11.0.0
2 clustered (active - passive) EV servers - Server 2008 R2
Each EV server handles 6 exchange nodes
Sani B.