Partager via


Slow mailbox move with Exchange 2010 SP1

I had complaints from some of my customers that moving users to Exchange 2010 SP1 system is slow and taking long time. In RTM Exchange was doing 5 parallel moves at a time due to the following settings:

RTM values:

MaxActiveMovesPerSourceMDB: This property indicates the number of mailboxes that can be moved on the source mailbox database at one time. The default value is 5 concurrent moves.

MaxActiveMovesPerTargetMDB: This property indicates the number of mailbox moves that can be moved on the target mailbox database at one time. The default value is 5 concurrent moves.

SP1 values:

MaxActiveMovesPerSourceMDB: This property indicates the number of mailboxes that can be moved on the source mailbox database at one time. The default value is 5 concurrent moves.

MaxActiveMovesPerTargetMDB: This property indicates the number of mailbox moves that can be moved on the target mailbox database at one time. The default value is 2 concurrent moves.

The change in MaxActiveMovesPerTargetMDB in SP1 means that we can only do 2 concurrent connections.

The workaround: check the values in the following file Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.config” and you can change MaxActiveMovesPerTargetMDB back to 5 to allow 5 concurrent moves.

Don’t forget to restart the Microsoft Exchange Mailbox Replication service and do this configuration change on all your CAS servers

Comments

  • Anonymous
    October 10, 2010
    Why was this changed?  Is this a bug? Can we expect a patch to change it back?

  • Anonymous
    March 01, 2011
    The comment has been removed

  • Anonymous
    March 27, 2011
    Why do microsoft change the value down to 2? Any technichal considerations?

  • Anonymous
    June 20, 2011
    Hi Sublemon, Did you install the hotfix to fix it?  install the hostfix on the cas/hub and mailbox server(cas/hub and mailbox are on the seperate servers)? Thank you and looking forward to your answer.

  • Anonymous
    June 28, 2011
    The comment has been removed

  • Anonymous
    November 23, 2012
    I have tried putting this as an article www.itbigbang.com/how-to-configure-and-improve-move-request-performance-in-exchange-2010

  • Anonymous
    December 26, 2014
    Exchange 4, 5, 5.5, 2003 mailboxes/databases use single instance storage (SiS) to insert pointers (only store the body and attachments once) to files/emails/attachments within exchange 2k3 db Instead of having multiple copies of the same data object stored within the db.

    SiS is removed in ex2007, 2010, 2013.

    2k3 mailboxes that are taking advantage of SiS have to expand during mailbox moves to 2007, 2010 databases.

    http://blogs.technet.com/b/exchange/archive/2010/02/22/3409361.aspx