Exchange Database Consistency Check - Fix the Error Instantly

A consistency check failure in an Exchange database usually indicates corruption in the EDB file, which can result from sudden server shutdowns, disk-related errors, or missing transaction log files. Such failures can make user mailboxes inaccessible, disrupt day-to-day business activities, and put critical data at risk. Prompt resolution is essential to regain access to mailboxes and ensure the integrity of your Exchange data.

While native tools like Eseutil can handle basic database repairs, they are often complicated and risky, particularly with severely damaged EDB files. EdbMails EDB to PST Converter, on the other hand, provides a safer and more streamlined recovery solution. This Microsoft-partnered tool can access and repair corrupted or offline EDB files without requiring the original Exchange Server or Active Directory. Additionally, it allows you to export mailbox data directly to PST format or migrate to Office 365 and live Exchange.

This detailed, step-by-step guide helps you resolve consistency check failures in Exchange server. Whether it’s due to a recent system crash or persistent corruption, EdbMails offers a fast and secure way to recover your data without the need for complicated scripts or manual configuration.

What causes the error ‘Exchange Database Consistency Check Failed’?

This error appears when the Windows Server Backup (WSB) tool is unable to complete a consistency check on the Exchange database. It usually happens due to a corrupted EDB file or missing transaction logs. When performing a backup, WSB compares the database with its log files to verify that everything matches and is up to date. If it finds any mismatches or the database isn't in a consistent state, the backup process fails and this error is triggered indicating that a reliable backup of the Exchange Server cannot be created.

Although you can choose to skip the consistency check during backup, doing so puts your data at risk. If the database is already corrupted or not in a healthy state, skipping the check may lead to an unusable backup, making data recovery impossible later on. Typically, the error message appears in the following format:

Consistency check for the component 'Code'\'Microsoft Exchange Server\ Microsoft Information Store\ Server' failed. Application 'Exchange' will not be available in the backup done at time '8/18/2020 7:52:10 AM'

How to check database consistency in Exchange 2003, 2007, 2010, 2013, 2016, and 2019?

To manually check database consistency in Exchange 2013, 2016, and 2019, use the PowerShell cmdlets New-MailboxRepairRequest -Database DatabaseName -CorruptionType and Get-MailboxRepairRequest. If you want to check the database consistency in Exchange 2003, 2007, or 2010, use the cmdlet eseutil/mh to see if the database is in the Clean or Dirty Shutdown state.

This allows you to check the consistency of the database and repair it before running the Windows Server backup tool. Let's look at how to fix the consistency error in the following section.

1. How to fix the error 'Exchange Database Consistency Check Failed'?

   To resolve the error, check the database consistency and attempt to repair it using Microsoft’s command line utility Eseutil, which displays the state of your Exchange database and allows for both soft and hard recovery.

   The Eseutil utility is installed in the native Exchange server directory and is compatible with all Exchange versions from 2003 to 2019. To check the status of your database file, first unmount it using the cmdlet Dismount-Database -Identity Database name.edb and make a backup copy in a safe location.

   Steps to repair the Exchange database and fix the consistency check error

   • Step 1: Launch the Eseutil tool from the Exchange server bin directory.
   • Step 2: Run the cmdlet eseutil/mh to check the state of the database.
   • Step 3: If the database is in the Clean Shutdown state, there are no errors.
   • Step 4: Run the cmdlet eseutil/k and eseutil/ml to check the state of log files.
   • Step 5: If the database shows Dirty Shutdown state, then it is most likely corrupted.
   • Step 6: Run the cmdlet eseutil/r to first perform a soft recovery.
   • Step 7: If the soft recovery fails, run the cmdlet eseutil/p to perform hard recovery.
   • Step 8: Finally, defragment the database and perform an integrity check.
   • Step 9: Run the Windows server backup tool after repairing the database.

   Keep in mind that while a hard recovery might fix issues in the Exchange database, it comes with the risk of permanent data loss. This method isn’t always dependable, and if it fails to restore the database, you may need to switch to a full recovery approach by converting the EDB file to PST using a trusted third-party tool like EdbMail. Additionally, using PowerShell cmdlets for the recovery process can be time-consuming and requires a solid grasp of technical procedures, which may not be ideal for every user.

2. Resolve database consistency check failure in Exchange 2019, 2016, 2013, 2010, 2007 using EdbMails

   EdbMails provides a reliable Exchange recovery tool designed to recover damaged EDB files from any Exchange Server version (2019–2003). It’s the perfect solution when tools like 'eseutil' fail or when backups show consistency check errors. With EdbMails, you can recover mailboxes even without log files or an active Exchange server. You have the option to restore data directly to a new or existing Exchange server or export mailboxes to PST format. Additionally, it allows you to create secure backups of your mailboxes for future use. Let’s go through the steps to repair an offline or corrupted EDB file using EdbMails.

   Step 1: Download and launch EdbMails EDB recovery software application

   • Download EdbMails and install the application on any computer running on Windows OS. You don't need to have an Exchange Server installed, the software works independently to help you access and recover mailbox data with ease.

     

   • Open the application and click ‘Login’ using your email ID and password. If you haven’t registered yet, click on ‘Start Your Free Trial’ to proceed.

     

   • Select ‘EDB Recovery (Offline) and Migration’ from the product list.

     

   • Select ‘EDB to PST’

     

   • You can either use the default job name or select ‘New Job’ to set a custom name that suits your preference.
   • Then, click ‘Next’ to continue.

     

   Step 2: Select the offline EDB file

   • Click ‘Browse for EDB file’

     

   • Browse and select the corrupted EDB file on your local drive that did not pass the consistency check during the Exchange backup process, then click ‘Next’ to continue.

     

   • Click ‘Browse’ to select the PST file location for saving the exported data

     

   • Choose a destination folder on your system for the exported PST files and ensure the selected drive has enough free space to accommodate the data without interruptions.

     

   • For Exchange Server 2003 and earlier versions, EdbMails automatically detects and locates the associated STM file from the same directory. In Exchange Server 2007 and newer versions, these files are no longer used, so no additional file is required.

     EdbMails then performs a thorough scan of the offline EDB file to recover mailbox data, even if the database is corrupted. The duration of the recovery process depends on the size and condition of the database, so it is important to allow the scan to complete fully before proceeding.

     

   Step 3: Select the mailboxes to export EDB to PST

   • Once the recovery process is complete, EdbMails automatically displays the recovered mailboxes within the application. Review and select the mailboxes you wish to export, then click ‘Next’ to proceed with the export process.

     

   Step 4: Convert EDB to PST

   • Review the selected mailboxes and folders to make sure all required data is selected. Once verified, ensure the ‘Action’ option is set to ‘Export’, and then click ‘Start Export’ to begin the process.

     

   • You can easily monitor the progress of the export through the progress bar. Once the export is completed, EdbMails will display a message confirming the successful operation.
   • EdbMails provides you the facility to pause and resume the EDB to PST export operation.

     

   • Click the ‘View Logs’ button to view the log report for detailed information about the number of folders, mailboxes and mail items that are exported.

     

   • Once the export is finished, you can open the PST file in Outlook to view and restore your mailboxes and folders. Additionally, EdbMails allows you to back up your Exchange server data for added security and recovery options.

Here are some of the main features that make EdbMails stand out:

1. Advanced include and exclude filter options to select the required items.
2. Directly import EDB file to Office 365 and live Exchange.
3. Recovers EDB files from consistency check failure.
4. Free EDB file viewer which allows you to view and preview specific mail items.
5. Export EDB to formats such as HTML, MHT and EML.
6. Advanced include and exclude filters that enable you to export Exchange emails to PST by specific date.
7. Compatible with Windows OS and Windows Server operating systems.
8. Supports recovering EDB files from Exchange 2003, 2007, 2010, 2013, 2016 and 2019.