The move request statistics can be viewed by running the below command:
Get-MoveRequestStatistics | Select DisplayName,StatusDetail,PercentComplete
We might get this because of large delays due to unfavorable server health or budget limitations. In most practical cases, we can notice this status when moving large mailbox batches of sizes more than 5GB.
These are the parameters controlling this:
The best solution for this is to move the large mailboxes in batches so that the system resources are sufficient to handle the migration.
Below are the major parameters that are controlling the migration on the Exchange 2016 servers:
“MSExchangeMailboxReplication.exe.config” file located at “C:\Program Files\Microsoft\Exchange Server\V15\Bin”
MaxRetries – 60, 0, 1000
MaxCleanupRetries – 480, 0, 600
RetryDelay – 00:00:30, 00:00:10, 00:30:00
MaxMoveHistoryLength – 5, 0, 100
MaxActiveMovesPerSourceMDB – 20, 0, 100
MaxActiveMovesPerTargetMDB – 20, 0, 100
MaxActiveMovesPerSourceServer – 100, 0, 1000
MaxActiveMovesPerTargetServer – 100, 0, 1000
MaxActiveJobsPerSourceMailbox – 5, 0, 100
MaxActiveJobsPerTargetMailbox – 2, 0, 100
MaxTotalRequestsPerMRS – 100, 0, 1024
- Ensure there is no file level antivirus running on the migrating target servers.
- Copy a 1GB file from the source server to the target server and verify the copy speed to ensure there are no network issues.
- Make sure there is no backup jobs running during the migration batch period.
- Better to initiate a small migration batch first of say 500 users and then open the perfmon during this period and monitor the memory, CPU, storage to make sure the resources are sufficient.
Brandon Stuart, PEI
This post is part of a series on Exchange Migration Status Messages. If you’re interested in learning more technical tips like this one, subscribe to our blog below!