Are you working to mount the dismounted Exchange 2013 database? Then the best course of action is to analyze the causes of Database issue, their probable solutions and decide for the appropriate course of action.
There are soft recovery and hard recovery options available to repair and restore Exchange database. Though employing the manual methods may mount the database, but an in-depth analysis of the pros and cons of the manual method is necessary to select the perfect solution, and considering the time required to run the soft Recovery and Hard Recovery commands, it is preferable to install a Mailbox Exchange Recovery Software.
First look into the probable cause of the problem, analyze the problem and then select the right solution.
Causes of Exchange in Dismounted state
- System updated, Transaction Logs overgrow after upgrade, resulting in disconnected Exchange database
- Database copy experiencing I/O error which can’t be repaired by the server on its own
- JET_errMissingLogFile -528 -548 – Exchange 2010 database recovery
Other Exchange errors may also result causing Exchange to slip into a dismounted state. Refer to the solutions and pick-up the best to mount the Exchange 2013 Database available in the dismounted state.
Steps to overcome error related to Transaction Logs grow rapidly after update
Exchange 2013 is smoothly updated to Windows 2012 R2 for better performance, however, the problem occurred when Transaction logs grow unevenly, and Exchange database is reported in discontinued state.
Steps to resolve:
- Check if the C:\ is full?
- Browse the location of Transaction Logs and delete all Transaction Logs. (Possible to delete Exchange DB only when the size is too small)
- Login back to Exchange Control Panel but the Exchange DB could not be mounted despite the fact the Exchange services are up and running
- Even after deleting the Transaction Logs, these are created fast and the problem remains as it is.
- When the above steps fail to resolve error, then try to reduce the time Exchange takes to create Transaction Logs to mount the Exchange DB again, without error.
- If the problem is not resolved then Check whether the database is in Clean shut down state before running the Log files. This can be done by running the clean shutdown command.
- Change the Log path from C:\
Run the Exmon command to fix the issue and proceed to mount the dismounted Exchange database 2013
Solution to overcome error when Database dismounts on its own
Exchange Server 2013 is running on Windows server 2012 but the server experiences I/O error, which is to be repaired. Even when the Exchange database size is just 25 GB, it keeps dismounting on its own and displays an error that “Database copy “#######” is showing I/O error that may be repaired”.
Steps to resolve:
- Try to identify the failure by Check checking the Event Logs for other storages and “ExchangeStoreDb” events.
- Service Recovery is also possible by failing-over to another copy, but the failover is also not possible due to the following error: “There is only one copy of this mailbox database “#######”. Automatic recovery is not possible”
- Repair the Exchange database using the ESEUTIL/P command and check if the I/O error is still showing.
- If it still shows the I/O error, then the problem lies with hardware related issues, to-be fixed by the Hardware vendor only.
Solution to overcome JET_errMissingLogFile -528 -548
Exchange Server 2013 is running on Windows server 2012 but the server experiences a JET_errMissingLogFile – 528 – 548; due to which Exchange server database is not mounted”.
Steps to resolve:
- Try to check the path of the database by running the ESEUTIL/mh. This command helps in identifying the state of Exchange Database – Clean shutdown state or Dirty shutdown state.
- For Clean Shutdown state, go to the Transaction Logs folder location, and move all the log-files and mount the stores.
- For Dirty shutdown state, check if the Log files which are indicated as Logs are available or not.
- After checking the Health of the Database, perform the Soft Recovery by running the command: “Eseutil /r <Log Prefix> /l “Path of the log files” /d “Path of the database”
- Mount the stores when the command completes successfully.
If the Soft Recovery does not complete successfully, select the database, take proper backup and try to run the Hard Recovery commands followed by Offline Defrag with Isinteg
Solution to resolve errors when the manual methods either fail or these take longer time-period to address the issue of database in dismounted state. The 4-step process resolves the database error and mounts the Exchange 2013 database available in the dismounted state.
The 4-Step Process to mount Exchange Database available in Dismounted State
This software ensures that database is available in mounted state when the 2013 database is in dismounted state. The gist of steps include:
“Select EDB File Scan a Preview and Save”
Steps to resolve:
- Download, install and register the software
- Select the database available in dismounted state
- Click on Quick Scan option to start the scanning procedure. For Extensive scanning, click on Extensive Scan option. Select multiple EDB files, if required.
- Click and select the Save options and the Exchange database files are saved in preferred format at specified location.
Option to export all mailboxes directly on Exchange server is also available. Fill-in the Login Credentials and export mailbox data directly on Exchange server.
In general, Exchange Administrators do not have enough experience working poweshell commands (eseutil) reason being; powershell commands are not needed on day-to-day basis, thus making it a less preferred choice. In such cases, a better option is to use Stellar Phoenix Mailbox Exchange Recovery Software to mount the dismounted Exchange 2013 Database.