Exchange 2010 DAG Passive DB stuck in "Failed and Suspended" Copy Status
We have a 3 server configuration for Exchange 2010 - 2 Servers with Mailbox & Hub Transport roles and 1 Server running CAS role. The 2 Mailbox servers, XCHMBS01 & XCHMBS02, are in a DAG and the Heartbeat witness is on the CAS.
A month or so back and unknown to us, we had an Exchange 2010 DAG database fail or ??? and the Active copy on XCHMBS02 became Active on XCHMBS01 and "Failed and Suspended" on XCHMBS02 yet the Copy Queue Length continues to grow. I ran the "Update-MailboxDatabaseCop
A source-side operation failed. Error An error occurred while performing the seed operation. Error: An error occurred while processing a request on server 'XCHMBS01'. Error: Couldn't open backup file handle for database 'Over2MDB' to server 'XCHMBS01'. Hresult: 0x50d. Error: A database backup is already in progress. Please verify that no other seeding or incremental reseeding operations are started for this database, and then try the operation again by rerunning the Update-MailboxDatabaseCopy
+ CategoryInfo : InvalidOperation: (:) [Update-MailboxDatabaseCop
+ FullyQualifiedErrorId : 4B7CB0C8,Microsoft.Exchang
I've done a lot of research, run multiple cmdlets, suggested scripts without any luck. All indications confirm the the Active DB is on the XCHMBD01 server yet I am unable to Resume or Update the copy and too leary to attempt Removing it.
Any suggestions ?
A month or so back and unknown to us, we had an Exchange 2010 DAG database fail or ??? and the Active copy on XCHMBS02 became Active on XCHMBS01 and "Failed and Suspended" on XCHMBS02 yet the Copy Queue Length continues to grow. I ran the "Update-MailboxDatabaseCop
A source-side operation failed. Error An error occurred while performing the seed operation. Error: An error occurred while processing a request on server 'XCHMBS01'. Error: Couldn't open backup file handle for database 'Over2MDB' to server 'XCHMBS01'. Hresult: 0x50d. Error: A database backup is already in progress. Please verify that no other seeding or incremental reseeding operations are started for this database, and then try the operation again by rerunning the Update-MailboxDatabaseCopy
+ CategoryInfo : InvalidOperation: (:) [Update-MailboxDatabaseCop
+ FullyQualifiedErrorId : 4B7CB0C8,Microsoft.Exchang
I've done a lot of research, run multiple cmdlets, suggested scripts without any luck. All indications confirm the the Active DB is on the XCHMBD01 server yet I am unable to Resume or Update the copy and too leary to attempt Removing it.
Any suggestions ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It worked. The key was finding the incorrect entry in Failover Cluster Manager and I had read so many posts elsewhere and picked up on a few configuration tips like restarting the service, that replication does not need to move across the Production network and to do a Replay as a starting point instead of starting with an Update. There is a lot of info out there on this error and just as many different scenarios so I was leary of forging ahead because there was no perfect match to my particular issue. I really hope someday this one saves someone else a lot of time, I spent about 2 days on this and the solution took about 2 hrs once I was headed in the right direction.
Is this the only DB affected ?
What is teh SP on both DAG servers respectively ?
- Rancy