Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, December 2, 2016 10:21 PM
Hi All,
Having problems with migrating some mailboxes - and cant understand the above message. I've turned off the 2nd servers in both 2010 and 2016 environments, so cant work out databases are trying to replicate?
I get this despite using the 'emergency' priority level when submitting the job. I thought that was supposed to force the server to allow it to run unhindered.
Advice appreciated.
Thanks
Craig
All replies (5)
Monday, December 5, 2016 9:37 AM ✅Answered | 1 vote
Hi Craig,
The MRS value should be on Exchange 2016 server, as below:
If change MRS value with no luck, I recommend you can upgrade Exchange 2016 to the latest version (CU3), and check again.
Moreover, as a reminder, there are only two roles in Exchange 2016, Mailbox and Edge, no CAS role anymore. For more information see Exchange 2016 architecture.
Niko Cheng
TechNet Community Support
Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, December 5, 2016 5:29 AM
As a workaround try to submit the new move requests by modifying the Priority to emergency or highest by running the below command.
New-MoveRequest -Identity Mailbox -TargetDatabase “DB Name” -BatchName Test -Priority Highest
Tweaking the Mailbox Replication Service configuration file:
https://thoughtsofanidlemind.com/2010/12/03/tweaking-the-mailbox-replication-service-configuration-file/
Additionally, here is an article which is related to Mailbox Migration Performance Analysis:
http://blogs.technet.com/b/exchange/archive/2014/03/24/mailbox-migration-performance-analysis.aspx
Also get help from this blog for migrating to Exchange 2016 using the Exchange Admin Center: http://mstechtalk.com/migrating-to-exchange-2016-using-the-exchange-admin-center/
Hope it helps.
Migrate mailboxes, Public Folders, Outlook profiles and rules and GAL etc. to-and-fro Exchange Servers and Office 365 with LepideMigrator for Exchange
Monday, December 5, 2016 6:45 AM
Hi Craig,
I met a similar issue before, it was caused by MRS Resource Health. We can disable it during mailbox migration as a workaround and check if any helps.
To Disable MRS Resource Health:
Regedit -->find the key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange ResourceHealth\MRS" --> set "MRS" REG_DWORD value from 1 to 0 --> Restart Exchange Mailbox Replication service
After migration is completed, we can revert back MRS value from 0 to 1 in regedit.
Hope this helps,
Best Regards,
Niko Cheng
TechNet Community Support
Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, December 5, 2016 8:34 AM
As in the original post I have already tried it with the 'emergency' priority.
Monday, December 5, 2016 8:36 AM
Hi Nico - Thanks for the helpful reply. I've already set it to this - I assume its on the 2010 and 2016 CAS servers? Actually, the ResourceHealth thread didnt exist on my 2016 servers but I have created it manually but to no avail - I still get the error.