Slow Mailbox Movement on Exchange 2013 SP1 Mailbox Migration


Slow Mailbox Movement on Exchange 2013  is the most common known problem where most of the Exchange Admin will face the issue while performing mailbox migration. Thought to share few steps that may help you to increase the speed of mailbox migration for your environment.

Exchange 2013 Mailbox Migration

1. Verifying the Protocol connectivity

Check there is no firewall block acrross the network if you are exchange server distributed across the WAN network.

Command: Test-MapiConnectivity -Identity Raji.s@mail.com | fl

If you are finding some error message..verify you have arbitration mailbox are located correctly on the respective Exchange server  (i.e Get-Mailbox -arbitration|fl Name, recipienttypedetails )

The other way to check using powershell command or use telnet command

$socket = new-object Net.Sockets.TcpClient
$socket.Connect(“server.mail.com”,135)
$socket.Connected
True

Telnet server.mail.com 135

2. If single mailbox movement is faster but when it goes to count more than 50 and resulting to get delay. Modify the value in the MSExchangeMailboxReplication.exe.config file

c:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeMailboxReplication.exe.config

MaxActiveMovesPerSourceMDB = “50″    
MaxActiveMovesPerTargetMDB = “50″    
MaxActiveMovesPerSourceServer = “100″    
MaxActiveMovesPerTargetServer = “100″    
MaxTotalMovesPerMRS = “100″

After performing the change make sure you restart the MSExchangeMailboxReplication service

3. Check out if there is an content index error on your mailbox database copies…seems to be bug in Exchange Server 2013 SP1 bug…Try to disable the index and check you can see the difference

Get-MailboxDatabaseCopyStatus  | ft name, status, contentindexstate,contentindexerrormessage

Set-MailboxDatabase DB -IndexEnabled:$False

4. Check out the NIC card drivers holds the latest drivers. Perfrom a test on copying 100 MB file from the source server to the target server. Try to the check it’s speed.  Verify with the hardware vendor is there any latest drivers got released for the server hardware. For Example in HP Servers (http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?spf_p.tpst=kbDocDisplay&spf_p.prp_kbDocDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c03734205-2%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken)

5. Disable the TCP Chimney

Check the TCP Chimney is Enabled and supported

Netsh int tcp show global

Netsh int tcp show chimneystats (Check the “Supp” value, if it’s “No” that means TCP Chimney is not supported or not enabled on the Network card driver settings, otherwise you’d see “Yes” with some values on “TMax” and “PMax”)

To disable TCP Chimney and RSS:

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

http://support.microsoft.com/kb/951037
http://blogs.technet.com/b/samdrey/archive/2013/12/02/exchange-2007-2010-2013-on-windows-2008-2008-r2-check-tcp-chimney-windows-settings-and-status.aspx

Few Powershell to analyze you Mailbox Movement:

1. There is a script written by Exchange Team – Follow the url for more detail – AnalyzeMoveRequestStats script – http://blogs.technet.com/b/exchange/archive/2014/03/24/mailbox-migration-performance-analysis.aspx

2. Get-MoveRequest | Where { $_.Status -eq “Completed” } | Get-MoveRequestStatistics | Select DisplayName,TotalMailboxSize,TotalMailboxItemCount,@{n=”Speed MB/min”; e={ [int]($_.BytesTransferred.ToMB() / $_.TotalInProgressDuration.TotalMinutes) }}

3. Get-MigrationUser | Group Status

4. Get-MoveRequest | Group Status

Advertisements

About Raji Subramanian

Nothing great to say about me...Just want to share my knowledge for others that will be useful at any moment of time when they stuck in critical issue....
This entry was posted in Exchange Server 2013 and tagged . Bookmark the permalink.

2 Responses to Slow Mailbox Movement on Exchange 2013 SP1 Mailbox Migration

  1. Steven says:

    Hi Raji,
    This is a great post. Helped me out. Thanks!

  2. selim says:

    Thanks for sharing your knowledge with us .Those are the things worked for me.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s