Mailbox Move Issues and Errors - Exchange 2010 to 2013

Question

I'm trying to move mailboxes from 2010 to 2013, but I'm experiencing a lot of issues.
My move batches keep hanging (stalled) for minutes and hours on end, and I can't seem to keep them going consistently.
I have two DAG's, one for Archive boxes, and one for Primary mailboxes. Each DAG has three members with DB copies of each DB. The npdes and the clusters themselves are up and healthy. However, at random some of the DB's Content Index state will go to Failed
or SuspendedandFailed. At which point I force a catalog refresh and DB index update, and it goes to healthy.
I've created the "ContentSubmitters" AD group (and assigned it permissions), reset the Search and Host controller services on each server, and restarted the Replication service. I also deleted and recreated the Index for each DB prior to restarting
services. No dice. I've also already moved the system mailboxes over to the 2013 databases.
I'm also getting some "Transient" errors in the user move log, things like this: 
Transient error ResourceUnhealthyException has occurred. The system will retry"
5/4/2014 8:43:55 AM [exmb1] The job encountered too many transient failures (60) and is quitting.
5/4/2014 8:43:55 AM [exmb1] Fatal error ResourceUnhealthyException has occurred.
Error: MigrationPermanentException: Warning: Target mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible. Error details: The store ID provided isn‎'t an ID of an item. --> MapiExceptionNetworkError: Unable to open entry ID. ‎(hr=0x80040115, ec=0)‎ Diagnostic context: Lid: 45025 Lid: 45345 StoreEc: 0x80040115 Lid: 22894 Lid: 24942 StoreEc: 0x80040115
Any ideas would be appreciated!!!

Answer 1

Hi 
I would suggest you to run the below command for this "My move batches keep hanging (stalled) for minutes and hours on end" issue and see the result
Get-MoveRequest -Identity "Mailbox Name" | Get-MoveRequestStatistics -IncludeReport | FL Report
Just check if the MRS health is fine by running the below command
Test-MRSHealth -Identity "CAS Server" -MonitoringContext $true | Export-CliXml "C:\temp\CAS_MRSHealth.xml" and look at the xml file to get more information
When I run the Test command against either of my CAS servers, I get: " 'EXCH1' does not have the right Exchange Server version or role required to support this operation."
Run i run that command against any of the mailbox servers, it completes and generates the XML file, but I'm not sure what I need to be looking for within that file.
The first command spits out a ton of data, here's a little excerpt:
5/5/2014 8:59:28 AM [exmb1] Transient error ResourceUnhealthyException has occurred. The system will retry
(2/60).
5/5/2014 9:00:02 AM [exmb1] The Microsoft Exchange Mailbox Replication service 'exmb1.contoso.com'
(15.0.847.31 caps:03FF) is examining the request.
5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
database 'newmbi', Mailbox server 'Exmb1.contoso.com' Version 15.0 (Build 847.0).
5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
database 'newarci', Mailbox server 'EXARC2.contoso.com' Version 15.0 (Build 847.0), proxy server
'EXARC2.contoso.com' 15.0.847.31 caps:1FFFCB07FFFF.
5/5/2014 9:00:07 AM [exmb1] Connected to source mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
database 'exmbi', Mailbox server 'Chsexmb2.contoso.com' Version 14.3 (Build 181.0).
5/5/2014 9:00:08 AM [exmb1] Connected to source mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
database 'Exarci', Mailbox server 'CHSEXARC1.contoso.com' Version 14.3 (Build 181.0)
5/5/2014 9:00:12 AM [exmb1] Request processing continued, stage LoadingMessages.
5/5/2014 9:00:36 AM [exmb1] Messages have been enumerated successfully. 6657 items loaded. Total size:
332.3 MB (348,411,982 bytes).5/5/2014 9:06:14 AM [exmb1] The long-running job has been temporarily postponed. It will be picked up
again when resources become available.