Hi Folks, 

we are working on a cross forest migration for AD and Exchange, where Source Exchange is 2010 SP3 and Target new Exchange is 2013 CU8. while migrating the mailboxes we are getting the below issues and it takes ages to complete. i have migrated one mailbox earlier with 4.7 GB size it after lots of retries it took 28 hours to complete. 

below is another mailbox which is quite smaller in size to check but i am still getting the same problem. what could be the cause for this. i have done all custom settings for MRS proxy and client binding at source Exchange server, but the results are still the same.

Informational: The request has been temporarily postponed because the mailbox is locked. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 6/19/2015 2:40:07 PM.

OverallDuration                         : 00:28:43.5949514
TotalQueuedDuration                   : 00:00:04.9658754
TotalInProgressDuration                 : 00:28:38.6290760
TotalStalledDueToHADuration             : 00:04:02.7186976
TotalStalledDueToMailboxLockedDuration : 00:12:38.8746309
TotalTransientFailureDuration           : 00:00:35.2813100
TotalIdleDuration                       : 00:04:50.2813457
TotalMailboxSize                       : 1.172 GB (1,258,052,697 bytes)
TotalMailboxItemCount                   : 37935
BytesTransferred                       : 343.6 MB (360,322,748 bytes)
BytesTransferredPerMinute               : 0 B (0 bytes)
ItemsTransferred                       : 24016

i am in a challenging situation, need urgent support.

This is not the place for urgent support.

Try restarting the Microsoft Exchange Replication Service.

hey Ed, i am in a challenging situation which led me type support instead of suggestions. 

btw i have done restarting the services, even i had to do some changes on source CAS server MSExchangeMailboxReplication.exe.config as below which even is not helping much. 

             <binding name="MrsProxyClientBinding"<o:p></o:p>

                 receiveTimeout="00:10:00"<o:p></o:p>

                 sendTimeout="00:10:00"><o:p></o:p>

          <reliableSession ordered="true" /><o:p></o:p>

          <textMessageEncoding><o:p></o:p>

            <readerQuotas maxArrayLength="3048576"<o:p></o:p>

                          maxStringContentLength="3048576" /><o:p></o:p>

          </textMessageEncoding><o:p></o:p>

          <httpsTransport authenticationScheme="Negotiate"<o:p></o:p>

                          maxReceivedMessageSize="3048576"<o:p></o:p>

                          allowCookies="true" />

<o:p></o:p>

any other suggestions, it like locking the mailboxes and trying it again and again until i cancel or it finishes which is causing me huge delay in moving every mailbox. 

I've never experienced what you're describing.  Have you looked at the report to see if it tells you anything?

Get-MoveRequest -Identity "Mailbox Name" | Get-MoveRequestStatistics -IncludeReport | FL Report

If you don't get a solution from that, you could try applying the newly released CU9, and if that doesn't fix it, open an incident with Microsoft Support.

Hi,

 

Any performance issues can cause this replication postpone issue?

You may need to use performance monitor tool to closely monitor the whole process of the replication.

 

Thanks,

 

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

Hi Simon, 

thanks for the response, doing the monitoring already and have directly engaged Microsoft team for the issue. will update once resolved.