Exchange Database Stuck in Disconnected and Resynchronizing? Try this.

Megha Sharma
Megha Sharma

Updated On - February 29, 2024

Summary: A DAG(Database Availability Group) is a high-availability and disaster recovery solution in Microsoft Exchange Server. In a DAG environment admin faces that the primary server is working fine. In contrast, the second server shows all databases stuck in a Disconnected and Resynchronizing state. Hence, only the primary database is in a healthy condition. In this guide, we have shared some solutions to fix the error through manual methods and Exchange recovery tools like Recoveryfix for Exchange Server.

Download Free

When an Exchange server is Stuck in a disconnected and resynchronizing state, it indicates a damaged or inaccessible Exchange database. In this case, you can wait and recheck the database status to resolve the error.
The following command will check the health of the Exchange database in DAG.
Get-MailboxDatabase -Status | Format-List name,server, mounted

In some cases, Manual techniques are required to repair the database and establish the connection between the exchange database and the associated server.

The typical error query faced by users looks like this:

Recommended Solution
Choose Recoveryfix for Exchange Server to recover corrupted/damaged Exchange databases and migrate mailboxes to multiple destinations with ease.

Causes of the error
The reasons behind this issue of the Exchange database being stuck in the disconnected and resynchronizing state could be many. Some of the possible reasons could be:

  • Lack of storage space in the backup server
  • Blocked TCP/UDP ports
  • Active Directory (AD) issues
  • Corruption in the database

Try these Manual Solutions
To fix this problem, you can try some hit-and-trial approaches using the possibilities mentioned above.

  • Check the Storage: Users can start by checking if the storage quota is filled up. Reach the drive which contains the log files and Exchange database file and check for the available storage in the disk. Exchange Server always requires at least 25-30% free space on the drive where databases are stored to operate in the DAG environment. If the storage space is filled, remove unnecessary data after dismounting the database and remount the database to see if the issue is resolved.
  • Check Port Connections: Sometimes unknowingly, ports are blocked by the network team while performing some other operations. Go to the Exchange Server settings and check whether these ports are blocked – TCP port 135 (for RPC), TCP port 64327 (for log shipping), and UDP port 3343 (for node communication). If found blocked, unblock the port.
  • Reseeding Failed Database Copy: Try this method if the database copy of the secondary Exchange Server has failed. In this method, the Exchange administrator creates a fresh copy of the failed database using the replication of the other Exchange database.

First, check the health status of the Exchange database copies in DAG by running this command in the Exchange Management Shell.

Get-MailboxDatabaseCopyStatus

This command will display Healthy, Mounted, or Failed and Suspended for Exchange database copies.
Now, you have the information which Exchange database copy is not healthy, You have two options for attempting to reseed the Exchange database – Exchange Admin Center and Exchange Management Shell.

Reseeding Failed Database Copy via Exchange Admin Center
Perform these steps.

  1. Open Exchange Admin Center and go to servers ≫databases. Select the database to be reseeded. On the right panel, you can see the details like database name, state, copy queue length, content index state, and other options. Click Update option.
  2. On the next Update database copy page, you can click browse and add the source server name (if you want) and click Save.
  3. The reseed process will get started. Wait for its completion, and after that, check whether the database state is changed.

You can also use cmdlets in the Exchange Management Shell to reseed the failed database copy.

Run this command to update the suspended database (if you are defining a source server)

Update-MailboxDatabaseCopy ” < enter Mailbox Database name > ” -SourceServer < enter source server name >

Execute this command for the update of the database (if the server is not defined).

Update-MailboxDatabaseCopy ” < enter Mailbox Database name > ”

After executing these commands, if you encounter any error for log files that these are already exist.

Update-MailboxDatabaseCopy ” < enter Mailbox Database name > ” – DeleteExistingFiles

It would delete the existing log files before starting the reseeding process.

The above-discussed manual solutions could help you fix the issue of Exchange database stuck in disconnected and resynchronizing state. But If the methods explained in this guide fail to fix the Exchange databases stuck in a disconnected and resynchronizing state. then we would recommend you, Exchange recovery software, like Recoveryfix for Exchange Server, to recover the mailboxes from the damaged database.
Recoveryfix for Exchange Server Recovery tool is a professional Exchange recovery tool that recovers corrupt or damaged Exchange database files to PST, live Exchange Server, or Office 365. It supports all Exchange Server versions, from oldest to newest, and supports selective data recovery.

Download Now

Conclusion

Due to different reasons like blocked ports, database corruption, storage issues, etc., there could be a disconnected state and resynchronizing issue with an Exchange database copy in a DAG. To fix this problem, you can try different methods. However, if the problem is database corruption, we recommend an excellent Exchange database recovery solution.

Leave a Reply

Your email address will not be published. Required fields are marked *

3  +  5  =  

Related Posts
Browse by Category