Read time 4 minutes

Summary: Windows Server Backup plays a vital role in data security for businesses, but issues like Exchange Consistency Check failures can arise. This article explores the causes and solutions for these errors, highlighting the use of ESEutil for database consistency checks. Additionally, it introduces Kernel for Exchange Server Recovery as a powerful tool for data recovery from damaged Exchange database files. Ultimately, ensuring data integrity remains paramount for organizations.

Ensuring the safety of data is of paramount importance for businesses. Regardless of their size, every organization manages substantial volumes of data, making data loss an unacceptable risk. Consequently, organizations employ a variety of backup strategies to guarantee the security and integrity of their critical data.

One valuable backup technique available is Windows Server Backup, a feature that offers comprehensive backup and recovery solutions for all applications within a Windows Server environment, including Exchange Server. However, despite its usefulness in safeguarding data, occasional issues may arise, such as Exchange Consistency Check failures.

Exchange Consistency Check by Windows Backup Application

The process is executed by the Windows Server Backup application, and its primary objective is to verify the integrity and currency of the Exchange Database snapshot being backed up. In simpler terms, it confirms whether the database backup contains all necessary information. This validation is achieved by comparing the contents of the database files with the data recorded in the log files, ensuring the consistency of the Exchange system.

Error Recorded During Windows Server Backup

While performing Exchange Consistency Check during the Exchange backup, the consistency check sometimes fails. The following error will be recorded by the application event log:

Log Name: Application
Source: Microsoft-Windows-Backup
Event ID: 517
Level: Error

Description: The backup started at “09/26/2018 5:22:45 PM” failed with the error code2155348010.” Please rerun the backup once the error is resolved.

Consistency Check Error Displayed in Event Log

On examining the application event log, you’ll get some other errors like:

Log Name: Application
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 “09/26/2018 5:22:45 PM.”

Cause of the ‘Exchange Database Consistency Check Failed’ Error

When performing a server backup or backing up the Exchange Server, a critical step involves conducting a consistency check on both the Exchange databases and log files. Unfortunately, there are instances when this consistency check fails, primarily attributed to missing or corrupt database files or log files. Consequently, when such a failure occurs, it results in the failure of the entire backup operation.

How to Resolve ‘Exchange Database Consistency Check Failed’ Error?

To address this issue, begin by identifying the impacted logs or databases. Once you’ve pinpointed the affected database, employ the built-in tool ESEutil to rectify the Exchange database consistency check problem. You’ll need to execute the ESEutil tool for each database and its associated log files to verify and rectify their consistency.

You can find the mailbox database and the associated log files at c:\program files\Microsoft\Exchange Server\mailbox\first storage group. Follow the below steps to run a consistency check against the mailbox database.

  • Dismount the mailbox database.
  • Open an Administrator command prompt.
  • Move to c:\program files\Microsoft\Exchange Server\mailbox\first storage group.
  • Now, to verify the log files, run ESEutil/K E00.
  • If any log file reports an error, move the log file to another location, remount the database and try to attempt the backup operation again.
  • Now, run ESEutil/K “Mailbox database.edb” to verify the mailbox database.

This solution is applicable to Windows Small Business Server 2011 Standard, as well as Windows Small Business Server 2008 Standard and Windows Small Business Server 2008 Premium.

After completing these steps, should you encounter any errors within the database, your next course of action will involve either restoring the database or initiating a database file repair. It’s worth noting that this approach primarily addresses minor issues, and there is no absolute assurance that it will fully resolve the problem. Additionally, it’s essential to be aware that utilizing ESEutil can be a time-intensive process.

How to Recover Data From Damaged Exchange Database Files?

Insufficient backup measures can leave you grappling with the task of data retrieval from compromised EDB files. Enter Kernel for Exchange Server Recovery, a sophisticated software tool designed to facilitate Exchange data recovery seamlessly. With this robust tool at your disposal, you can effortlessly create backups of your Exchange mailboxes and conveniently store them in your preferred location. What sets this tool apart are its intelligent filtering capabilities, which empower users to selectively back up data according to item type, date, and even exclude specific folders.

This tool is enriched with some smart features that enhance the performance. Some of the extensive features are:

  • Recover mailboxes from corrupt/damaged EDB files
  • Migrate Exchange mailboxes to Office 365, Outlook, or Live Exchange
  • Directly Export EDB emails to PST, EML, MSG formats
  • Extracts Exchange data from backups created by any application

This versatile tool is capable of extracting Exchange data from a variety of file formats, including .bkf files generated by Windows NT/Symantec Backup Files, .fd files produced by HP Backup Files, and .ctf files created by CA ARCserve Backup Files.


The Windows Server backup feature conducts a crucial consistency check on the Exchange application during the backup process. Occasionally, this check may uncover errors that lead to a failed Exchange backup. Fortunately, in the majority of instances, you have the option to address this issue manually. Nevertheless, in scenarios where robust Exchange data backups are unavailable, it is possible to recover valuable Exchange data from the corrupted files.

Kernel for Exchange Server