How to Fix Exchange Database Consistency Check Failed in Simple Steps
Summary: Users face this error Exchange database consistency check failed when they take the backup of Exchange database via Windows Server Backup. The issue shows that there is the possibility of inconsistency & due to this the back cannot be used in the future to restore the EDB as well as mailboxes. This write-up explains the error, the reason why it occurs, and the solution to fix the error by using the ESEUTIL utility and advanced Exchange Server Recovery third-party software.
Nowadays everyone who is using Exchange Server knows the importance of its data and to keep it safe & secure users have to backup the Exchange data. There are various solutions available and one such method is Windows Server Backup (WSB) which helps them to backup & restore the Exchange database in the Windows Server.
But sometimes while backing up the data via WSB, users might face an error message i.e. Exchange database consistency check failed due to various reasons. Don’t freak out, here we will provide a manual and an advanced solution that will help you get rid of the issue.
Overview of Exchange Database Consistency Check Failed Error
Users use WSB (Windows Server Backup) to backup and restore the mailbox database in the Windows Server. A plug-in is used for WSB in Microsoft Exchange which allows users to make VSS (Volume Shadow Copy Service) for the backup in Exchange.
In the backup process, the Window Server backup runs a consistency check on the Exchange data files to make sure that they are consistent. So, it can be used for recovery but if the consistency check fails and then it displays the following error which shows that there is a backup failure and it cannot be used for recovery.
“The application will not be available for recovery from this backup. The Consistency check was failed”
Major Reasons Responsible for this Error Message
When users use the WSB to backup the Exchange database, it executes the consistency check between the mailbox database & log files. The reason for consistency check fails is because of missing or corrupted EDB and log files, which leads to the backup failure and error or issue is logged.
Users can see the error report given below:
Manual Way to Fix the Exchange Database Consistency Check Failed Error
To resolve this error first users have to find the exact log and Exchange database file which is affected. After that, launching the ESEUTIL utility to fix the Exchange consistency check failed. Run this tool for each transaction log file and mailbox database for the consistency checkup.
To check the EDB and log, execute the following command:
Eseutil g “e:\program files\exchsrvr\mdbdata\priv1.edb”
Follow the steps given below for the consistency checkup in the mailbox:
Step 1: The first solution is to disable the EDB consistency check.
Note: Doing this restricts users to restore the mailbox database in future
Step 2: The second solution involves the use of an in-built utility i.e. ESEUTIL.
This utility will help in the verification of EDB and complete log file before backup the mailbox database via Windows Server backup. This might fix the Exchange database consistency check failed error.
Run the command given below to run an Exchange mailbox health check and log file:
eseutil /mh name_of_the_database.edb
eseutil /ml name_of_log_file.log
Run the following command if there is an integrity and consistency error in the Exchange database.
Eseutil /p name_of_database.edb
This command repairs the Exchange database but it’s a time-taking process. It is not sure whether this will remove the issue or not. Plus, the user may have to face another error like:
“Operation terminated with the error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 0.920 seconds”
Advanced Solution to Get Rid of the Corruption Issues
Exchange Server Recovery Software is a professional tool that provides two scan mode options i.e. Quick and Advance scan mode which removes corruption from the Exchange database and repairs Exchange mailbox as well as EDB file without losing any data. For minimal corruption, select the quick scan and if the Exchange database is highly corrupted choose the advance scan option.
The recovery manager for the Exchange database tool supports offline / dismounted Exchange database files and exports the healthy and recovered mailboxes to the Live Exchange Server, Office 365, and multiple data files. Users can easily extract mailboxes from EDB file Exchange and export them to multiple file formats.
Any technical and non-technical users can use the advanced software. It easily exports any size of EDB file in bulk. It provides an interactive graphical user interface that eases users’ work and saves their time and effort.
Bringing It All Together
Now users have detailed information about the error, how it occurs, and most importantly solutions to fix the Exchange database consistency check failed issue. In case the manual solution doesn’t work or repairs a corrupt EDB file, then users can use the advanced software described in the above section.
