Tuesday , December 12 2017

Move Fail : Mailbox Changes Failed to Replicate

Error: Mailbox Changes Failed to replicate . Database doesn’t satisfy the constraint second copy because commit time isn’t guaranteed by replication time.

  • Verified NTP is fine,
  • Time zones are fine.
  • Verified all DAG members showing same time.
  • They are in Same VLAN in same site. (In my Case its a three node DAG , 2 on primary , 1 on Second Site.)
  • Database Replication seems to be healthy.
  • Replication link seems to be healthy.

Even Smaller Mailboxes tend to fail with same error.

image

To workaround this error : We temporarily set DataMoveReplicationContraint to None

image

Set-mailboxdatabase DatabaseName -DataMoveReplicationConstraint None

Mailboxes moved to new databases without any errors instantly.

About Satheshwaran Manoharan

Satheshwaran Manoharan is an Microsoft Exchange Server MVP , Publisher of CareExchange.in Supporting/Deploying/Designing Microsoft Exchange for some years. Extensive experience on Microsoft Technologies.

Check Also

Enable Password Write back on existing Azure AD Connect

By Default Azure AD Connect synchronizes password one way only , From On-Premises to Cloud ...

2 comments

  1. Nobody ever read this article, or tried this solution? There is a typo: DataMoveReplicationContraint instead of DataMoveReplicationConstraint.

Leave a Reply

Your email address will not be published.