This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 2%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAN%3C/text%3E%3C/svg%3E)
Moving user mailbox in Exchange Server 2016 DAG Active Database to another Active Database on another member gives following errors
Mailbox migration stops at 95 % giving the below error
Error: MigrationMRSPermanentException : Error: Mailbox changes failed to replicate: Database c0c1dbe-12f4-45b5-8498-51756a2ffc5c doesn’t satisfy the constraint Second Copy because the commit time 11/16/2022 5:00:16 AM isn’t guaranteed by replication time
Hi @azhar Nasim
Thank you for contacting Microsoft Open Specifications Support. After reviewing your post, it appeared it does not fall within guidelines outlined under https://aka.ms/openspecs, I am removing [Exchange Server Open Specifications] tag from the post.
Hung-Chun Yu
Microsoft Open Specifications Support
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 80%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Hi @ azhar Nasim ,
Just checking in to see how things are going on with this thread.
If the reply was helpful, you can click the "Accept Answer" button under this post so that other's with similar question can benefit from this thread as well.
If you still have further questions or concerns, feel free to post back.
Is replication good between those databases?
Get-mailboxdatabasecopy
You can bypass the restriction, but I would look at the health of the databases first.
Set-mailboxdatabase -identity <target database> -DataMoveReplicationConstraint None
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 98%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Please remove the failed move request and create a new one by adding the skipmoving parameter:
New-MoveRequest -identity <mailbox> -skipmoving:folderviews,folderrestrictions -TargetDatabase <database>
And see if the shared mailbox can be moved successfully.
Set-MailboxDatabaseCopy cmdlets in the Exchange Management Shell to view and configure database copy settings, such as replay lag time, truncation lag time, and activation preference order. For detailed steps to view and configure database copy settings, see Configure mailbox database copy properties.