Share via

Remote move migration doesn't finalize

  • Applies to: Exchange Server

Symptoms

When you initiate a remote move migration by using the Exchange admin center (EAC) or the New-MoveRequest PowerShell cmdlet, the migration to the target mailbox database doesn't finish, and it returns the following error message:

Cannot enter finalization because Data Guarantee is lagging behind by more than 00:05:00. Failure: Database GUID doesn't satisfy the constraint SecondCopy because the commit time 7/1/2022 2:35:10 PM isn't guaranteed by replication time 12/31/9999 11:59:59 PM

Cause

The DataMoveReplicationConstraint setting for the target mailbox database is set to SecondCopy. This is the default value if the system or administrator added a second mailbox database copy. The SecondCopy setting requires that at least one passive database copy meets the Data Guarantee API criteria for health, replay lag time, and copy queue length. The error message indicates that the migration didn't finalize because no passive database copy met the maximum replay lag time criteria.

Resolution

Use the appropriate method, depending on the direction of the move request and whether the target mailbox is in a database availability group (DAG):

  • For offboarding, if the target mailbox is in a DAG, use one of the following methods:

    • Run the Get-MailboxDatabaseCopyStatus PowerShell cmdlet to view the health and status of the mailbox database copies. Diagnose and fix a mailbox database copy, then restart the migration.

    • Restart the remote move migration to a mailbox database that meets the Data Guarantee API criteria.

    • Set the DataMoveReplicationConstraint to None by running the following command in the on-premises Exchange Management Shell (EMS):

      Set-MailboxDatabase <target mailbox database GUID> -DataMoveReplicationConstraint None

  • For offboarding, if the target mailbox is not in a DAG, use the following method:

    • Set the DataMoveReplicationConstraint to None by running the following command in the on-premises EMS:

      Set-MailboxDatabase <target mailbox database GUID> -DataMoveReplicationConstraint None

  • For onboarding, use the following method:

    • Remove the move request, and then retry the migration. If the error reoccurs, contact Microsoft Support.