Microsoft Exchange Server 2013: Mailbox and High Availability

Planning mailbox moves

It is common practice to initiate a set of mailbox moves to happen overnight when user activity and network traffic are light. You should be careful not to swamp the network with many concurrent move requests for large mailboxes that conflict with other network-intensive activities such as nightly backups. You should also distribute moves across all available servers and databases to minimize the chance of swamping a target server with the load from multiple incoming move requests, all of which generate significant CPU and I/O demand to populate the new mailboxes and update content indexes. Another issue to consider is the limits MRS imposes on moving information to different mailboxes and servers. For example, if you want ...