How to Fix the Error: Exchange Database Stuck In Disconnected and Resynchronizing?
Summary: This write-up will provide complete information to solve the error “Exchange database stuck in disconnected and resynchronizing”. Also, the user will get to know the cause of the error and the solution to fix it.
Microsoft Exchange Server plays a very important role in an IT organization and other industry verticals around the globe. Everyone knows that it is very prone to corruption and other issues which made trouble for the Exchange database or other data in it. The Exchange Server is setup by using DAG where the two servers joins together and form one Exchange access server along with database copies with each other.
Sometimes in the Database Availability Group the Exchange user and IT administrator come across the error where the secondary EDB stuck in disconnected and resynchronizing. Then users will face the failure in the secondary Exchange database whereas the primary DB is in healthy state/condition.
Before proceeding to the solution, let’s look at the query given below that is commonly asked by users:
Know the Reason/Cause Of “Exchange Database Stuck In Disconnected and Resynchronizing” Error
There could be many reasons behind this error. Here we have mentioned some of the possible cause behind this issue:
- Database corruption
- Problem occurred in Active Directory
- Space size issue in secondary server
- Blocked ports such as: Transmission Control Protocol (TCP) / User Datagram Protocol (UDP)
Recommended Solution: Use SysTools Exchange Server Recovery software to remove corruption from the offline / dismounted Microsoft Exchange database file and repair Exchange mailbox. This recovery manager for Exchange database tool provides Quick and Advance scan option that recover & repair EDB file which is severely damaged or corruption with no data loss and export the mailboxes directly to Live Exchange Server, Office 365, and multiple file formats in a hassle freeway.
Use Manual Solution to Fix the Error: Exchange Database Stuck In Disconnected and Resynchronizing
1. Check Storage On Secondary Server
The first and foremost thing is to check whether the storage on the secondary server is completely filled because the storage is the primary requirement for smoothing running of the Database Availability Group. Also, check the drive which stores the EDB and transaction log files, and see the storage space in the disk.
If it is filled, then remove unimportant data after when you dismount database Exchange 2016, 2013, 2010 and mount it back to see if the error is fix/resolved.
2. Check the Connection of Port
While performing other tasks or operations sometimes the network team mistakenly block by them. Navigate to the Microsoft Exchange Server settings & see if the following ports which are given below is being block or not. If it is blocked, then unblock it.
– TCP Port 135 for “RPC”
– TCP Port 64327 for “Log Shipping”
– UDP Port 3343 for “Node Communication”
3. Reseed the Failed Database Copy
Users can use this solution when the secondary sever database copy has failed. Here, the Exchange admin create the fresh copy of failed Exchange database by using the replica of another database.
Insert the following command given below to check the health of Exchange database copes in Database Availability Group.
Get-MailboxDatabaseCopyStatus
It shows the healthy, failed, or suspended and failed for Microsoft Exchange database copies. You can use the EAC and EMS to reseeding the failed database copy.
Use Exchange Admin Center
Step 1: Login to EAC > Navigate to Servers > Databases. Choose the Exchange database to reseed. On the right side user will see the details such as: DB name, content index state, etc… > Then, click on the update option
Step 2: Update the Exchange database copy page > Click on the browse button > Add the source server name > Select the save button
Step 3: Then the reseeding process will started > Wait for time till the completion process will complete > Then check the state of database and see if it changed
If users are defining the source server then insert the command given below to update the suspended database
When the server isn’t defined then insert the cmdlet to update database
If you come across any error in the transaction in the log file then use the command given below:
Before starting the reseeding procedure it doesn’t deleted the log file
This manual solution is help users to resolve the error “Exchange database stuck in disconnected and resynchronizing”. But if the cause behind this issue is corruption then it is suggested to use the Exchange Server Recovery software provided by SysTools.
This is the advanced recovery tool that easily recovers the unhealthy / damaged / corrupted Exchange database file without any data loss. It extract mailbox from EDB File Exchange 2016/2013 after recovery and export it directly to the Live Exchange Server, Office 365 and HTML, PST, EML, MBOX, MSG, PDF file format in a simplified way.
Bringing It All Together
Now users can fix the error ”Exchange database stuck in disconnected and resynchronizing” easily by use the manual solution provide in this write-up. If the problem occurred because of corruption then user can use the recovery solution that resolve the database corruption Exchange 2010, 2013, 2016 in an easy way without losing any data.