Database that stays in "Resynchronizing" status for ever
-
Thursday, December 22, 2011 9:16 AM
Hi,
My current configuration consists of 2 Exchange 2010 SP1 RU5 servers, with DAG.
One called Mail1 and a new installation called Mail2 that was installed yesterday.
I've disabled replication on the MAPI network, and the replication happens between two dedicated NICs.
When I attempt to add mailbox database copy for one of my databases, it copies the DB to Mail2, then it says in the status "failed and suspended".
When I try to update the database copy, it just stays in resynchronizing status and it's copy queue length rises.Any help would be appreciated, thank you.
All Replies
-
Friday, December 23, 2011 12:12 AM
Make Sure your NIC bindings are same.
-
Friday, December 23, 2011 2:23 AM
Hi,
Please try below suggestion:
1 Update-MailboxDatabaseCopy -Identity <DatabaseCopyIdParameter> -DeleteExistingFiles
2
a. Suspend database copy.
b. Dismount mailbox store.
c. Remove all the transaction log and checkpoint files.
d. Mount the stores and then reseed the database.Rowen
TechNet Community Support
- Marked As Answer by Rowen-Xu Saturday, December 31, 2011 3:56 AM
-
Friday, June 15, 2012 5:06 PM
Hi,
Please try below suggestion:
1 Update-MailboxDatabaseCopy -Identity <DatabaseCopyIdParameter> -DeleteExistingFiles
2
a. Suspend database copy.
b. Dismount mailbox store.
c. Remove all the transaction log and checkpoint files.
d. Mount the stores and then reseed the database.
Rowen
TechNet Community Support
Step b (& 1/2)
Ensure dismounted DB is in a consistent state (Clean Dismount) before removing any transaction logs.
No need to waste copy time if your just going to have to copy them back and monkey with the database further.
.png)
