“Exchange Database Clean Shutdown State won’t mount” – [SOLVED]
If you are working on Exchange Server environment, then there are chances that you come across of a situation where Exchange database does not mount. The reason could be routine repair cycle or just a normal reboot. If you launch EAC i.e. Exchange Admin Centre, you will be getting status of Update. In addition, if you launch Exchange Management Shell (EMS), it shows databases as dismounted.
General Overview
- Checking DAG Status
- Run Eseutil command to check the state of database, if it is healthy or not.
- Checking Failover Cluster Manager
- Update content index
- Use CubexSoft EDB Repair software to fix and export all EDB mailboxes
Run the given mentioned command to check the above:
Get – Mailboxdatabasecopystatus *
When you try to mount Exchange database manually, you will get a long error message and command just hang when it runs.
Now, check database shutdown status. In the same Exchange Management Shell, run following command to check database status, make sure the given command should executed from Elevated EMS:
Eseutil/mh
After the command ran, it displays all databases are in “clean shutdown” state, but why Exchange database won’t mount?
The copies index state of Exchange database showing “Failed” as it logs an event ID of 1009. Below is sample of error that appears:
At this point, running the below mentioned command will not run if database is in dirty shutdown state.
Eseutil/p
Make use of the command if it is entirely corrupted. The reason behind saying this is that, one could potentially have some level of loss of data.
Moreover, you will come across the errors logged in event viewer present in the application log concerning database and corresponding copies:
The next thing would be looking at DAG (Database Available Group) itself. It can be performed by opening Failover Cluster Manager on the Server. We are not going to make modifications but checking the cluster state, if it is healthy or not.
After it gets opened, view event logs for cluster and if you see next to cluster name, you will observe red X in case of errors.
In failover cluster manager, expand DAG name and view members, you will notice if they all are in healthy state or not. In this scenario, more than one DAG member was appearing as offline that result in quorum loss so the databases not mount.
Now, reboot the servers that are in offline state and start them, observe server health in failover cluster manager, once it become online, give it few minutes to make it settle and then reboot next server.
After all reboots done, members showing offline now should be online and if you again go back to EMS (Exchange Management Shell), check copy status of DAG, you will notice that database is now mounted.
When you ran eseutil /p command, one need to create new mailbox database and implement mailbox moves, as the state of that database is not healthy.
The last step is to retrieve database copies index state back to healthy one. Try updating copy from Exchange Admin Center or run the below command from EMS:
Update-Mailboxdatabasecopy – “<Database Name>” –Catalogonly
In case, if it fails, try another command mentioned below that help in updating the copies by discarding existing ones and allowing it re-seed the database copy.
Note: The process will take time, depending on the size of the Exchange database.
Update-MailboxDatabaseCopy”<Database-Name>” –DeleteExistingFiles
Still, if it does not work, make use of professional EDB Repair application. The software smoothly fix all errors of Exchange database file and facilitate to export EDB to PST, PDF, MBOX, EML, O365, Live Exchange Server and more.
In order to check the entire process, download the free demo of the application that allows to repair and move first 25 files per folder from EDB mailbox into required file type free of cost.
Note: To take full benefits of the software, it is necessary to have the license key.
