{"id":711,"date":"2017-11-14T04:50:34","date_gmt":"2017-11-14T04:50:34","guid":{"rendered":"https:\/\/www.kerneldatarecovery.com\/blog\/?p=711"},"modified":"2023-06-14T12:22:44","modified_gmt":"2023-06-14T12:22:44","slug":"how-to-deal-with-slow-moving-mailboxes-while-performing-exchange-2013-migration","status":"publish","type":"post","link":"https:\/\/www.kerneldatarecovery.com\/blog\/how-to-deal-with-slow-moving-mailboxes-while-performing-exchange-2013-migration\/","title":{"rendered":"How to deal with slow moving mailboxes while performing Exchange 2013 migration"},"content":{"rendered":"

When the Exchange Administrator provides all the essential resources to a migration batch, it should run faster and quickly. Suppose the migration batch is sluggish even when you are running a single batch, and the hardware resources are also better. In that case, there are maximum chances that the migration batch will be stuck in the queue or show an error after a prolonged hanging.<\/p>\n

This blog discusses how you can intelligently deal with the problem of slow Exchange 2013 Migration and what best practices can users adopt while taking the big move to ensure enhanced migration performance.<\/p>\n

Recently, I recall one of the IT administrators of a mid-sized organization calling me up and saying that his mailbox migration from Exchange 2010 to 2013 is going slow. He wondered what might be causing this despite having a considerably fast network and ample resources to carry out the migration operation. The only concern he had was \u2013 how to accelerate the Exchange 2013 migration without any data losses! Well, it\u2019s not the story of a single IT administrator. In the past few months, I\u2019m encountering many such IT administrators who get extremely worried when movement of mailboxes in Exchange 2013 is actually annoying and crawls at a snail\u2019s pace. Anyways, this is what that dragged me into writing this piece for all the IT folks out there who\u2019re struggling with their Exchange 2013 migration issues. So, let\u2019s dive in for the solution!<\/p>\n

Do you Actually Need to Panic? How to Identify Exchange 2013 migration is actually running slow!!<\/h4>\n

As per thorough testing & analysis by Microsoft technical team, it was revealed that in ideal conditions a single mailbox migration to Exchange Server 2013 is likely to move at the speed of 300 MB to 1 GB per hour with approximately 20 concurrent hops running between 10 GB and 15 GB per hour.<\/p>\n

Though, under real-world conditions, one must not expect transition speeds of more than 6 mbps even on a fast speed internet connection. Needless to say, if your migration is going on at a frequency that is less than the figures mentioned above, your Exchange 2013 migration is actually running slow. Also, if the mailbox moves aren\u2019t reaching to completion, it\u2019s time to do something to troubleshoot migration issues.<\/p>\n

If you\u2019re wondering what might be the cause of slow migration, I must mention the fact that Exchange 2013 enforces a very strict throttling policy that hinders the migration to run smoothly. Always be sure that you\u2019ve disabled throttling policy before you start migrating from an older version to Exchange 2013.<\/p>\n

Also, one can adopt a better way to avoid such issues by performing test migrations and get a rough estimate of the throughput with respect to the configurations used.<\/p>\n

Possible Solutions to Speed-up your Exchange 2013 Migration<\/h4>\n

By now, you must have identified whether or not you actually have a problem with your migration. Henceforth, it\u2019s time to speed-up your Exchange 2013 migration & enhance its performance.<\/p>\n

\n
Solution 1<\/strong><\/div>\n
\n

As per Microsoft\u2019s technical support team, by default one can migrate only 2 mailboxes at a time. This migration speed is acceptable when your server is running at high loads since increasing the frequency of transitioning mailboxes can lead to lengthy server access times during a busy session. Also, if your CPU is sitting idle and not utilized fully (performing not more than 25%), you must consider increasing the number of mailbox migrations running at a particular period of time.<\/p>\n

To increase the number of mailbox migrations, perform modifications in the config file \u2013 MSExchangeMailboxReplication.exe.config<\/code>, which is residing on your FrontEnd Servers. You will find this file at the location \u2013\u2018C:\\ProgramFiles\\Microsoft\\Exchange Server\\V15\\Bin\u2019<\/code>.<\/p>\n

Now you can make changes as per your desire by modifying the following values that possess the below marked settings by default. This includes the maximum active moves per source, per target, per source server and per target server along with the maximum total requests per MRS and export buffer size in KBs.<\/p>\n

MaxActiveMovesPerSourceMDB=\u201d20\u2033
\nMaxActiveMovesPerTargetMDB=\u201d20\u2033
\nMaxActiveMovesPerSourceServer=\u201d100\u2033
\nMaxActiveMovesPerTargetServer=\u201d100\u2033
\nMaxTotalRequestsPerMRS=\u201d100\u2033
\nExportBufferSizeKB=\u201d512\u2033<\/p><\/blockquote>\n

After accomplishing all the desired changes, you will have to restart the Exchange Mailbox replication in order to allow changes to take effect.<\/p>\n<\/div>\n<\/div>\n

\n
Solution 2<\/strong><\/div>\n
\n

For greater impact on the speed, the most effective solution to increase migration speed is to utilize the parameter \u2013 \u201c-priority emergency\u201d during the movement of mailboxes. If you\u2019re wondering what magic does this parameter leaves on mailboxes; I must mention that using this parameter using the following command (refer to command only as an example) will move your mailbox to the highest priority in the MRS (message recovery services) queue.<\/p>\n

New-MoveRequest -Identity \u201cdemo_user@yourdomain.com\u201d -TargetDatabase \u201cDB1\u201d -Priority emergency<\/code><\/p>\n<\/div>\n<\/div>\n

\n
Solution 3<\/strong><\/div>\n
\n

Unfortunately, even if after trying the above two solutions, you\u2019re still struggling with slow mailbox moves; then the problem may be occurring because you might haven\u2019t disabled MRS throttling. For disabling this, just go to the following registry and make changes in the \u201cMRS\u201d REG_DWORD key by modifying it from the previous value i.e. 1 to the new value i.e. 0<\/p>\n

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\services\\MSExchange ResourceHealth<\/code><\/p>\n

Now, you will need to restart the Exchange Mailbox Replication Service by moving your mailboxes without enforcing any throttling policy. Observer the migration speed. Once you\u2019re done with the migration process, just change your value back to 1 by re-enabling MRS resource monitoring.<\/p>\n<\/div>\n<\/div>\n

The Final Note<\/h4>\n

We have shown you all the possible solutions that will allow you to run a quick migration, and you can any solutions based on the symptom of your migration batch problem. If the slow migration harasses you regularly, you should use Exchange Migration<\/a> Software, and it will run a separate migration batch and amplify the speed for migration. You can choose unlimited data during migration and schedule it at any convenient time.<\/p>\n

\n
\"Download\"<\/a><\/div>\n<\/div>\n\n\n