Read time 4 minutes
Exchange Server is a core part of business communication. Therefore, it’s essential for organizations to take regular backups of Exchange databases. A reliable backup method is to use the built-in Windows Server Backup (WSB) feature. Before taking the complete backup of the database, the WSB runs a consistency check to see if the database is healthy. Sometimes, due to missing transaction logs or corruption in the database, the EDB file becomes inconsistent. In this situation, WSB gives an “Exchange database consistency check failed” error and terminates the backup. When this error occurs, the following event is recorded in the Event Viewer:
Source: Microsoft-Windows-Backup
Event ID: 565
Level: Error
User: System
Description: Consistency check for component “03ed71c2-8671-4a21-b15e-1715913543c” \ “Microsoft Exchange Server\Microsoft Information Store\CONTOSOSERVER” failed. Application “Exchange” will not be available in the backup done at the time “03/26/2026 5:22:45 PM.”
To resume the backup process, the database must be fixed and brought to a consistent state. In this condition, the user can either use ESEUTIL for Exchange Server repair or, if the corruption is severe, try a professional Exchange repair software.
Why does the consistency error occur in the Exchange database?
In the Exchange database file, the consistency issue occurs when the data in the database does not match the uncommitted transaction log files. This situation can happen due to:
- Power Failure
- Server Crash
- Human Error
- Virus Attack
How to check the health of the database file and log files?
- Go to the location “C:\Program Files\Microsoft\Exchange Server\V15\Bin\”
- Select the eseutil tool, right-click and choose Run as administrator
- To check log files, run this command: eseutil /ml “log-files-complete-path”
- To check edb file, run this command: eseutil /mh “edb-file-complete-path”
In the output of the above command, check the value for the State property. When the database is in an inconsistent state, it shows Dirty Shutdown. To fix the problem, try the method below.
How to fix ‘Exchange database consistency check failed’ error?
Before proceeding with repair, make sure to create a backup of the database. However, since the EDB file is inconsistent, it must be dismounted from the server. For backup, you must copy the database along with its log files and paste in a safe, isolated location.
This is important because the native method can delete data. With a backup copy, we can later try to restore deleted Exchange mailboxes.
Steps to fix EDB file consistency issues error:
- Open the eseutil tool as an administrator.
- First, we will try the soft recovery method. This will not delete any data items in the database during recovery. Run this command in the command line tool:
eseutil /r “log-prefix” /l “log-file-path” /d “edb-file-path.edb”
- Now, check the database health using /mh. If the EDB State is still Dirty Shutdown, it means the soft recovery fails.
- When soft recovery cannot repair the EDB file, we use the hard recovery method. Run this command: eseutil /p “edb-file-path.edb”
- Again, check for EDB file health. This time, the State will show Clean Shutdown.
- Now run the database defragmentation command:
eseutil /d <db-complete-path-with-filename.edb> /t <temporary_path-with-filename.edb>
- Finally, mount the database using the Mount-Database cmdlet in the Exchange Management Shell (EMS)
What if the EDB file state still shows as Dirty Shutdown?
When the database state is not changed to Clean Shutdown after using the esetuil command, it means your EDB file is severely corrupted. In this situation, we don’t recommend running the eseutl command multiple times, as it will lead to massive data loss. A smart approach here is to use a dedicated Exchange database recovery tool that can scan and repair severely corrupt Exchange database files.
One such tool is Kernel for Exchange Server. The tool helps admins to safely repair single or multiple EDB files with built-in filters for user-specific recovery. After repair, admins can either save the recovered data locally (to Outlook PST) or restore the EDB to Live Exchange.
Conclusion
Leaving the database in an inconsistent state will dismount the EDB from the server, stopping the workflow. Fix it as soon as possible using the eseutil utility. However, if the ‘Exchange database consistency checks failed’ error occurred due to corruption, use the Kernel for Exchange Server to recover the mailboxes with metadata and folder structure preserved.
