This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 15%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERT%3C/text%3E%3C/svg%3E)
Hi all.
Here is an interesting question i can't see to find the answer to on Google, we have an Exchange 2016 infrastructure, 4 nodes across 2 data centres, one data centre has 2 active Exchange servers both hosting the active copies of all 18 databases we have, the secondary DR data centre has passive copies of all 18 databases - just in case!
My question is - we want to balance the number of mailboxes across all our active databases (currently some databases have hundreds of mailboxes where others have <30!) - so need to carry out a number of move requests, lets say we move mailbox 1, a 20GB mailbox from database 2 to database 3 what would happen to the passive copies, would it move the mailbox locally on all the passive servers (given it already has a copy on database 2 and just needs to migrate it to database 3) or would it replicate that 20GB mailbox from the active copy of its new home on database 3 to all passive servers - both in the primary and secondary data centre - which would of course generate a significant amount of traffic over our inter data centre network?
Any ideas?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
As Andy mentioned, the changes made to Exchange databases are first stored in the transaction logs, later the transactions would be committed to the database file.
For your reference: Transaction logs in Exchange 2013
In a DAG deployment, the logs would be replicated from the active copy to the passive copies.
I am writing here to confirm with you how thing going now?
If you have any questions or needed further help on this issue, please feel free to post back.
Its going to generate logs during the move request on the destination server that holds the active database copy, then that will replicate logs to all the passive copies.