Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, October 3, 2011 4:02 PM
Hello
I have 3 Mailbox Servers in a DAG
When migrating larger mailboxes 1GB+ to their new database I am getting this error.
Error: Move for mailbox '/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=MBX1' is stalled because DataMoveReplicationConstraint is not satisfied for the database 'mdb1' (agent MailboxDatabaseReplication). Failure Reason: Database 1541069d-2976-4f40-afb1-569ed323de0b does not satisfy constraint SecondCopy. There are no available healthy database copies.
I am assuming that this is the copies getting behind. The problem is this does not happen until we are at 95% and that mailbox has been unavailable for several hours.
I have read some posts about changing the Database constraints, but can not find the parameter/syntax for this.
Would it be easier to remove the COPIES for now, move the mailboxes, then re-add the copies ?
Thank You
Oh here is the error
Error: Move for mailbox '/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=MBX1' is stalled because DataMoveReplicationConstraint is not satisfied for the database 'mdb1' (agent MailboxDatabaseReplication). Failure Reason: Database 1541069d-2976-4f40-afb1-569ed323de0b does not satisfy constraint SecondCopy. There are no available healthy database copies.
All replies (17)
Monday, October 3, 2011 4:17 PM âś…Answered | 1 vote
I think this one is easy.
SecondCopy means that at least one passive mailbox database copy must have the most recent changes synchronized for the move to occur (this is the default value).
So you have two options:
1. Set this setting to None:
Set-MailboxDatabase <DB_Name> -DataMoveReplicationConstraint None
2. Or make sure you have at least an healthy copy of that database.
Run the following command to check the status of all the copies:
Get-MailboxDatabaseCopyStatus <DB_Name>
Hope this helps!
http://LetsExchange.blogspot.com
Monday, October 3, 2011 4:12 PM
The database you are moving the mailbox to, is it in a healthy state??
Check this technet link - it provides 3 different solutions to this issue (look under "No available healthy database copies (FC: -2147220223 | ID: MSExchange Mailbox Replication 1100)")
Troubleshooting Mailbox Moves
http://technet.microsoft.com/en-us/library/dd638094.aspx
Thank you, Ibrahim Benna MCSA+Messaging, MCSE+Messaging,MCITP, MCT, MVP "Did you backup your Information Store Today?!"
Monday, October 3, 2011 6:02 PM
I think this one is easy.
SecondCopy means that at least one passive mailbox database copy must have the most recent changes synchronized for the move to occur (this is the default value).
So you have two options:
1. Set this setting to None:
Set-MailboxDatabase <DB_Name> -DataMoveReplicationConstraint None
2. Or make sure you have at least an healthy copy of that database.
Run the following command to check the status of all the copies:
Get-MailboxDatabaseCopyStatus <DB_Name>Hope this helps!
Looks like we are Healthy on both databases and all copies. So I am going to try the -DataMoveReplicationConstraint to NONE
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus pdc-exec-1
Name Status CopyQueue ReplayQueue LastInspectedLogTime ContentIndex
Length Length State
PDC-Exec-1\IS-BHMEXCH1 Healthy 0 0 10/3/2011 10:49:48 AM Healthy
PDC-Exec-1\IS-AUSEXCH1 Healthy 0 0 10/3/2011 10:49:48 AM Healthy
PDC-Exec-1\IS-PDCEXCH1 Mounted 0 0 Healthy
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus pdc-exec-2
Name Status CopyQueue ReplayQueue LastInspectedLogTime ContentIndex
Length Length State
PDC-Exec-2\IS-BHMEXCH1 Healthy 0 0 10/3/2011 10:49:48 AM Healthy
PDC-Exec-2\IS-AUSEXCH1 Healthy 0 0 10/3/2011 10:49:48 AM Healthy
PDC-Exec-2\IS-PDCEXCH1 Mounted 0 0 Healthy
[PS] C:\Windows\system32>
I will try this tonight and let y'all know how it goes. Thank You !!!
Monday, October 3, 2011 6:13 PM
- You might have to clear the current move request then try moving again after changing the DataReplicationConstrain to NONE.
Sukh
Tuesday, October 4, 2011 7:44 AM
- You might have to clear the current move request then try moving again after changing the DataReplicationConstrain to NONE.
Sukh
Sukh is right, if the move request is Queued, you can simply resume it. If it actually failed, you might have to remove it and re-do it again.
Isn't the database called MDB1?! Or you changed the name in your first post?
http://LetsExchange.blogspot.com
Tuesday, October 4, 2011 4:08 PM
OK guys that worked perfectly !
1. Checked the status to make sure they were OK
2. Set DatabaseReplicationConstraint to none
3. Moved the mailboxes which moved alot faster !
4. Did the Happy Dance
If not too much trouble, should i change the DatabaseReplicationRestraint back ? If so what is the parameter ?
Thank You !!!
Tuesday, October 4, 2011 9:15 PM
You should change it back to the default of SecondCopy. To do that, use the same Set-MailboxDatabase command I mentioned before:
Set-MailboxDatabase <DB_Name> -DataMoveReplicationConstraint "SecondCopy"
However, I would definately find out why it didn't work with SecondCopy if all the copies where Healthy...
http://LetsExchange.blogspot.com
Tuesday, June 13, 2017 6:35 AM
Hi!
Its mandatory run command: Set-MailboxDatabase <DB_Name> -DataMoveReplicationConstraint "SecondCopy" ?
Tuesday, June 13, 2017 6:53 AM
I have exact same problem:
DatabaseName Status CopyQueueLength ReplayQueueLength MailboxServer ContentIndexState
mdb01 Mounted 0 0 MBEX1 Healthy
mdb01 Healthy 38 1 MBEX2 Healthy
Some mailboxes moved ok (<5Gb), but move take a lot of time, but large mailboxes failed with error :
Error: Move for mailbox '/o=LO/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=usermbx' is stalled because DataMoveReplicationConstraint is not satisfied for the database 'mdb01' (agent MailboxDatabaseReplication). Failure Reason: Database 99819658-2ce6-405e-82fa-ddc9116d442f does not satisfy constraint SecondCopy. Some database copies are behind. Could you please enplane step-by-step action to fix this problem
Tuesday, June 13, 2017 1:19 PM | 1 vote
What's the output of the following cmdlet?
Get-MailboxDatabase | Get-MailboxDatabaseCopyStatus
http://LetsExchange.blogspot.com
Wednesday, June 14, 2017 4:33 AM
Hi Nuno!
Status SecondCopy, i was chnage now to None. Was delete all failed job and created ne move request. right now i`m waiting.... Do you know some different way to move user mailboxes to another server, maybe non Microsoft tool, which quicker move mailboxes?
Thursday, June 15, 2017 2:40 AM
Hi AZSt,
You should never use any other method of moving mailboxes other than the in-built ones!
If your mailboxes are not being moved, then you need to investigate why as there is something wrong in your environment that you need to fix.
Run this for your move requests and check the current status/error:
Get-MoveRequest | Get-MoveRequestStatistics | FL
http://LetsExchange.blogspot.com
Friday, June 16, 2017 8:58 AM
Thanks a lot
Right now moving is OK..
Monday, June 19, 2017 7:12 AM
Hi Nuno
I have a trouble with mailbox database where i moved users mailboxes, log files lun is full. backup job failed.
How to fix this issue?
Monday, June 19, 2017 11:25 AM
Assuming the database is nor part of a DAG, use the Move-DatabasePath to move the database to another location.
http://LetsExchange.blogspot.com
Tuesday, June 20, 2017 1:40 PM
Database is part of DAG, and have a copy
Wednesday, June 21, 2017 2:46 AM
In that case, and assuming you can't expand the disk volume, you'll have to remove the database copy and use the Move-DatabasePath cmdlet.