26 C
Dubai
Tuesday, April 16, 2024

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.

Satheshwaran Manoharan
Satheshwaran Manoharanhttps://www.azure365pro.com
Award-winning Technology Leader with a wealth of experience running large teams and diversified industry exposure in cloud computing. From shipping lines to rolling stocks.In-depth expertise in driving cloud adoption strategies and modernizing systems to cloud native. Specialized in Microsoft Cloud, DevOps, and Microsoft 365 Stack and conducted numerous successful projects worldwide. Also, Acting as a Technical Advisor for various start-ups.

Related Articles

2 COMMENTS

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

LEAVE A REPLY

Please enter your comment!
Please enter your name here

× How can I help you?