Last updated on September 25th, 2021 at 03:59 pm
Sometimes, there comes a situation where the exchange database does not mount in Exchange Server. This usually happens due to a normal reboot.
Because of this issue when users open EAC i.e. Exchange Admin Centre, they got a status of “updating”. And if the user launches EMS i.e. Exchange Management Shell, it shows a message that the databases are dismounted.
Manual Method to Resolve Clean Shutdown State Won’t Mount issue
Firstly check the shutdown status of the database. Run EMS to check the status of the database.
Run the given command in Exchange Management Shell:-
After using this command successfully, a statement appears that all the databases are in a “clean shutdown state”. But now the question is why the Exchange databases but then won’t mount
The answer is the copies index state of the Exchange Database usually displays as “failed” and it logs an event ID of 1009.
Run the following command to resolve this problem
Only use this command if the Exchange database is entirely corrupted or in a clean shutdown state.
Using this command in another situation, have a chance of creating some data loss issues.
The next steps are to check the DAG i.e. Database Availability Group Database
- It can be evaluated by opening the Failover Cluster Manager on the server.
- After opening it, event logs for the cluster are viewed and if we observe next to the cluster name, we can observe a red, if there is an error.
- If more than one DAG Members appear as OFFLINE, then there is quorum loss and the databases are not mounted.
The servers that are in the offline state should be rebooted and then again started.
After some time, the server settles down after it becomes online and then again reboots the next server.
After the completion of all the reboots if we again move to EMS i.e. Exchange Management Shell and check the copy status of DAG.
Then it is found out that the database is finally mounted.
The final step is to retrieve database copies index state to a perfectly healthy one. One should try to update a copy from the Exchange Admin Center.
Update– Mailbox database copy- Name of the database- Catalog.
The above command should be applied to update.
An automated solution to Resolve Clean Shutdown State Won’t Mount Problem
If a user is facing any type of issue in the Exchange Server EDB file and wants to get a solution to easily get it repaired and recover all its internal items, then the user should use a program named eSoftTools Exchange Server Database Recovery Software.
This tool repairs the corrupt EDB file and recovers all its inner database like emails, contacts, tasks, notes, and many more. It also can be utilized to easily convert Exchange Database stored EDB files into multiple different file formats like- PST, EML, EMLX, MSG, and HTML.
Advantages of EDB Recovery Software
- It has a simple GUI along with the quick recovery of EDB to PST with the data consistency.
- By converting, EDB to PST, the internal data will not face any type of risk.
- The information on the Exchange server can be opened without any data loss.
- There is no limitation on the basis of file size.
- The deleted folders and emails can be recovered by this software.
- This software even has the ability to recover private and public folder databases.
Basically, the manual method is not such favorable and has some disadvantages & also it is a very lengthy procedure to resolve error as described above. So, a reliable third-party tool like the eSoftTools EDB to PST converter is a perfect method used to recover the exchange data efficiently and securely. Through this method of Converting EDB as a PST file users will get the facility to open Exchange mailboxes in all versions of MS Outlook, even the 2016 version.