Solving DataMoveReplicationConstraint when moving large mailboxes

During a transition in one of my customers, when trying to move a large mailbox between Exchange Server 2010 servers, the following error was being displayed, and the move process was going to failed state.

Error: Move for mailbox ‘/o=OrgName/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=name.lastname’ is stalled because DataMoveReplicationConstraint is not satisfied for the database ‘DB03-GOLD’ (agent MailboxDatabaseReplication). Failure Reason: Database c79c6393-32fe-4ef3-abfd-d5deda6b07fc does not satisfy constraint SecondCopy. Some database copies are behind.


The first step is to check that the source mailboxes are being replicated among their DAG members and there is no replication issues, if that is the case, fix that and try again. However, in some larger mailboxes we may continue getting that error, and we are going to show you how to identify the issue and a possible workaround for the situation.

Using Exchange Management Console, expand Recipient Configuration, click on Move Request a list of all mailboxes that are being moved will be listed, double click on the failed one or just click Properties.


Click on the Details tab, we can see the error on the Suspend Comment as shown in the image below.


So, if you validate the replication and you are still getting the error message, the following cmdlet can remove the requirement of having a second copy of the database before the move process. The first cmdlet will list the current setting that you have at Mailbox Database level, and afterwards we will change to None.

Get-MailboxDatabase <database> | ft Name,Server,DataMove* –AutoSize

Set-MailboxDatabase <Database>  -DataMoveReplicationConstraint None


After that remove all failed entries and start the move process again.