Consider the following scenario:
You have a Microsoft Exchange Server 2010 server that is configured as follows:
The target mailbox database has a passive copy.
The DataMoveReplicationConstraint property on the target mailbox database is set to something other than None.
For more information about how the DataMoveReplicationConstraint property works, see Exchange 2010 Mailbox Moves and Mailbox Resiliency.
The mailbox server that hosts the passive copy has the DatabaseCopyAutoActivationPolicy property set to Blocked.
You install the Service Pack 3 Rollup Update 3 (KB2891587) for Exchange Server 2010.
In this scenario, when you try to move mailboxes, the move request stops at 0% without giving an error message. Additionally, when you run get-MailboxDatabaseCopyStatus, it reports the passive copy is healthy.
This issue occurs because Microsoft Replication server marks the status of the passive copy as Failed even if the passive copy is healthy. Be aware that Get-MailboxDatabaseCopyStatus does not show the status of the passive copy as Failed in this situation. The failed passive copy status is something that is internal to the Microsoft Exchange Replication service code logic.
To resolve this issue, install the following update rollup:
2936871 Update Rollup 6 for Exchange Server 2010 Service Pack 3
To work around this issue, use of the following methods.
Set the DatabaseCopyAutoActivationPolicy property on the mailbox server that hosts the passive copy to IntraSiteOnly or Unrestricted. For example, you can use Windows PowerShell as follows:Set-MailboxServer –identity MBX2013 – DatabaseCopyAutoActivationPolicy Unrestricted
Move the mailbox.
For more information, see Set-MailboxServer.
Set the "DataMoveReplicationConstraint" property on the target mailbox database to None. For example, you can use PowerShell as follows:Set-MailboxDatabase -identity "TargetDatabase" -DataMoveReplicationConstraint None Note To make the change take effect immediately, you have to restart the Microsoft Exchange Replication Service.
Move the mailboxes.
Change the "DataMoveReplicationConstraint" property back to its original setting.