Your Exchange database plays a significant role in the smooth functioning of your organization’s email communication. Maintaining its health is essential. This is possible through routine tasks like persistently monitoring logs, taking regular backups, and ensuring hardware stability.
Even after taking the necessary steps, the chance of database corruption is hard to rule out. In any such case, the database can become inaccessible and trigger a Dirty Shutdown state.
This will cause the email system of your entire company to crash, necessitating a quick Exchange server recovery. You can opt for database restore from VSS Backup, or use the built-in ESEUTIL utility to serve this purpose. Alternatively, experts also prefer using Exchange recovery software for quick and easy recovery. Here is a detailed insight into this topic.
How does the Exchange database become corrupt?
Several issues affecting the Exchange server can make the database inaccessible, damaged, and corrupt. Some of these issues are as follows:
- Hardware failure: Old hardware may find it difficult to withstand real-time email traffic, leading to bad hard drive sectors.
- Server crash: Redundant requests often cause server overloads, misconfigurations, and network disruptions, eventually leading to server failure.
- Abrupt system shutdown: An accidental shutdown of the system due to a power outage or other reason can affect the update of transaction logs. This results in database inconsistencies and corruption.
- Oversized database: The Exchange database often exceeds the size limit mentioned in the registry, making the database corrupt and causing it to dismount.
- Malware attack: A virus intrusion or a malware attack can severely disrupt system services, leading to boot failure or OS failure.
- Manual glitches: An accidental file-handling mistake, a misconfiguration, running a defective server-cleaning tool, or a bulk mailbox deletion or export by an authorized user can also cause Exchange database corruption.
- Disk storage issues: A hard drive running out of space fails to write data properly, resulting in frozen transaction logs or incomplete data blocks. This is also one of the reasons behind corruption.
Using ESEUTIL to Repair an Exchange Database
ESEUTIL is a native command-line tool by Microsoft that checks the database status. Depending on the outcome, it carries out soft or hard recovery. When soft recovery becomes ineffective, hard recovery is a crucial mode for Exchange recovery. Since the latter method permanently purges irrecoverable or corrupt data from the database, admins rarely recommend it. You should try this only when you are ready to accept data loss.
Prerequisites for Using the ESEUTIL Tool
Keep the following in mind before performing any operation on the Exchange database via ESEUTIL:
- Backup of the Exchange database file
- Admin permissions to access the Exchange database
- Ample storage space for the recovered database
Steps to Repair the Database
1. Locate the ESEUTIL File
Usually, it resides in the Bin directory of the Exchange installation. In Exchange 2013 and 2016, the file’s default location is C:\Program Files\Microsoft\Exchange Server\V15\Bin\. For other versions, the location may differ on your system.
2. Check the Database Status
To find the existing status of the Exchange database, run the ESEUTIL /mh command:
- Open Exchange Management Shell (EMS) as an administrator.
- Use the command below to change the directory path to the path of the ESEUTIL file: cd C:\Program Files\Microsoft\Exchange Server\V15\Bin
- Next, run the ESEUTIL command: ESEUTIL /mh <Path_To_Database_Folder>
- As a result, you will see the database header with a list. Look for the State field in this list.
- If the state is Clean Shutdown, you can mount the database on the server.
- If it shows Dirty Shutdown, proceed to the next step.
3. Perform Soft Recovery
If the Exchange database has minor corruption, you may opt for soft recovery. This method replays the transaction log files to change the database state from dirty to clean shutdown. It also maintains data integrity without causing data loss during the process.
The soft recovery command is as follows: ESEUTIL /r <Path_To_Database_Folder>
Depending on the size and performance of the database, the command may take some time to complete.
4. Recheck the Database State
To find out the outcome of the soft recovery command, run the ESEUTIL /mh command again: ESEUTIL /mh <Path_To_Database_Folder>
If the Dirty Shutdown state still exists, proceed with hard recovery.
5. Perform Hard Recovery
⚠️ Warning: This command results in the loss of data, as it removes all inaccessible and corrupt data from the Exchange database. Consider it a last resort. You will receive a warning about data loss before the recovery starts.
Use the following command to perform hard recovery: ESEUTIL /p <Path_To_Database_Folder>
This will make your database reusable, but with some data loss. To avoid this drawback, administrators prefer using automated solutions for complete recovery without losing data.
Repair an EDB File with Exchange Server Recovery Software
Using Exchange server recovery software is an easy and quick way to repair a corrupted Exchange database. While ESEUTIL is a Microsoft utility that recovers an inaccessible database with considerable data loss, an automated recovery tool can safely fix the database without altering your original EDB file.
How Can Exchange Recovery Software Help?
It can help restore a dismounted or corrupted Exchange database file with extreme precision. Alongside, you can also use it to recover mailbox items, such as emails, contacts, notes, attachments, and other items. Here are some of the common advantages of using these Exchange recovery applications:
- Resolve the Dirty Shutdown issue by repairing the EDB file
- Fix the “Couldn’t mount the specified database” error
- Recover mailboxes from EDB files of a crashed Exchange Server
- Recover data from a virus- or ransomware-affected Exchange server
- Export recovered mailboxes to Office 365 (Microsoft 365) or directly to a live Exchange Server
- Perform eDiscovery and granular recovery on mailboxes, folders, and specific emails
Of the many tools fulfilling these needs, Stellar Repair for Exchange is a viable option to consider. It is available in different versions so you can choose the one that fits your needs. You can also opt for the browser-based free Exchange database repair service, which restores mailboxes up to 5GB for quicker recovery.
Conclusion
Exchange database corruption can occur due to sudden shutdowns, disk issues, malware, or other server problems, often leaving the EDB in a Dirty Shutdown state. In such cases, administrators can use ESEUTIL /mh to check the database status and ESEUTIL /r for soft recovery. If this fails, ESEUTIL /p can perform hard recovery, but it may cause permanent data loss and should be used only as a last resort.
For a safer recovery approach, Exchange recovery software can repair corrupted or inaccessible EDB files while recovering mailbox data. Stellar Repair for Exchange can help recover emails, attachments, contacts, calendars, and other mailbox items from damaged Exchange databases. Thus, while ESEUTIL can be effective for Exchange database repair, professional recovery software is a better option when data preservation is a priority.
