im currently migrating (550 users)  Exchange 2007 SP3 RU12 to Exchange 2013 CU7

the source (2007) server is located in a different AD site

the mailbox move is extremly slow.

sometimes the current move stalled with the message

Relinquishing job because of large delays due to unfavorable server health or budget limitations.

is did some research on the source and target server, but no resource constrains.

can somebody point me in the right direction?

already tried on the source server

netsh int tcp set global rss=disabled
netsh int tcp set global chimney=disabled

the current connection between the two servers is 100Mbps

a completed user reports als high values for TotalStalledDueToWriteThrottle

but the desntination server is running fine, no latency issues at al.

sometimes a queued users that is copying messages stalls with RelinquishedWlmStall

details of that users

reports Relinquishing job because of large delays due to unfavorable server health or budget limitations.

resource configuration 2007 server

4 vCPU's

16 GB Memory

2008 R2 Server

resource configuration 2013 server

8 vCPU's

32 GB Memory

2012 R2 Server

• Edited by robcee Friday, February 13, 2015 11:47 AM

during the mailbox movement from source to target,  enabled Replications for both MAPI(LAN) and Replications network on DAG , after finish mailbox movement, you can disable. (if replications is disabled on LAN NIC- which is recommended  )  , it's believed you have high speed NIC for LAN.

also move maximum 4 mailboxes from same database  up to maximum 5 databases at same time( 20 mailboxes),

• Edited by Indunil Tuesday, February 17, 2015 6:26 AM add

Hi robcee,

Does this issue occur when you try to migrate Public Folder?

Do you have TMG? If yes, please try to check whether the TMG block the HTTP request from the Exchange 2013.

• Open the Forefront TMG Management console.
• In the tree, click Monitoring, and then click the Alerts tab.
• Check whether a warning that contains the following text is displayed: The number of HTTP requests per minute from the source IP address IPAddress exceeded the configured limit. Forefront TMG will block new HTTP requests sent from this IP address.

 

Thanks

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi Marvis,

the public folder migration went very fast (it was only 700MB).

it only occured when migrating mailboxes.

the migration duration was about one week.

there is no TMG in between or firewall.

Hi, Robcee.

I have the similar situation.

1. To get the statistics about the process I am using:

• get-moverequest|get-moverequeststatistics|ft-autosizeDisplayName,StatusDetail,TotalMailboxSize,TotalMailboxItemCount,PercentComplete,BytesTransferredPerMinute,TotalStalledDueToMailboxLockedDuration,TotalStalledDueToWriteCpu,TotalStalledDueToWriteThrottle

And all my requests have very big TotalStallDueToWriteThrottle (10 hours or more, but yes I have very large mailboxes 20, 30, 40)

• and scripts from here - http://blogs.technet.com/b/exchange/archive/2014/03/24/mailbox-migration-performance-analysis.aspx

The scripts from the link above showed me IdleDuration about 88%, which means that the migration process waits for resources but! CPU, RAM, Network are not busy at all.

2. Tried to investigate network problems - nothing found

3. Edited MRS config file to allow more simultaneous connections (according to this https://social.technet.microsoft.com/Forums/windowsserver/en-US/23a5cc4c-e66a-4468-b079-24414aa1ca66/slow-migration-exchange-2007-to-2013-cross-ad-site?forum=exchangesvrgeneral)

- migration requests count increased, but migration speed was still the same, just more requests were Relinquished

Yesterday

1. I've changed ExportBufferSize from 512 to 10240 in MRS config file.
2. Restarted Microsoft Exchange Mailbox Replication service, Microsoft Excahnge Replication, Microsft Exchange Throttling

As a result migration process became 3 time faster than before.

Please try to increase the ExportBufferSize and let me know if it helped.