How to Resolve Exchange Database Consistency Check Failures

For businesses, Exchange Server acts as the root directory for data management. This necessitates taking regular backups of the data through various techniques to ensure its utmost safety and security. Among all the widely used methods, Windows Server Backup (WSB) is a crucial backup technique. 

An integral part of the Windows Environment, it provides upscale Exchange Server backup and recovery options. Nevertheless, at times, it may face an Exchange consistency check failure while backing up the database. Here, we will discuss this error and try to resolve it through Eseutil, a manual method, and by using a professional Exchange recovery tool such as Stellar Repair for Exchange.

What is the Exchange database consistency check failure?

Windows Server Backup (WSB) runs a consistency check on the EDB files to check if they are consistent and ready for recovery. It ensures that the database backup is the most recent and the log file consists of all the details and events taking place since the last backup. By detecting the database consistency results, WSB saves time in analyzing data from various sources and reconciling them.

However, in case of a failed consistency check, it will finish the backup with the warning as given below, based on your Exchange Server version. 

“The application will not be available for recovery from this backup. The consistency check failed.”

If you encounter this error message, it may indicate corruption in your EDB file, leading to a failed backup, which cannot perform database recovery. 

What is the reason behind the Exchange database consistency check failure?

During the consistency check, WSB compares the log files with the information in the database to match the information and ensure its updated status. A mismatch or an inconsistent state of the database will trigger an error regarding backup failure, citing its inability to create a reliable Exchange Server backup. This happens mainly because of missing transaction log files or a compromised EDB file. 

You may also come across this failure message if the database used is inconsistent, already dismounted, or in dirty-shutdown state. To recover from such situation you should repair or restore the database from a recent good backup.

 The error may also surface because of an issue with Volume Shadow Copy Service (VSS) writers. Notably, VSS settings are essential in Exchange to ensure application-consistent backups and data integrity. Any error in these settings can lead to consistency check failures in the Exchange database.

Resolving the Consistency Check Failed Error using Eseutil

One instant way to fix this issue could be to disable the Exchange database consistency check in the WSB. However, it will stop you from restoring the Exchange database from the backup. A comparably better way is to check the exact Exchange log and the affected EDB file. Next, launch the Eseutil, the built-in utility, and run the tool to check the consistency for every transaction log file and mailbox database. Here are the commands to fix the issue:

This Eseutil command will check the transaction log and EDB files:

Eseutil /g "C:\program files\exchsrvr\RDBdata\priv1.edb"

 This will check the logical integrity of the Exchange database and its inconsistency in read-only mode.

Here are more commands:

1. This Eseutil command will check details about the current state of the database

Eseutil /MH database_name.edb

2. This command will check details about the current state of the log files

Eseutil /ML  file_name.log

3. If you find any kind of error in the consistency or integrity of the Exchange database, proceed to repair the database by running the command below:

Eseutil /P database_name.edb 

Here, you should be aware that the Eseutil command is suitable to fix minor issues; it may not be effective in resolving bigger problems like this. Moreover, it takes considerable time, and there is no guarantee of error resolution either. Chances are higher that you get the following error message on using this built-in tool.

Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 0.936 seconds.

To overcome the limitations of the Eseutil utility, you can switch to a reliable, result-oriented, and professional exchange recovery tool. This is where Stellar Repair for Exchange can work effectively.

Resolving the error using Stellar Repair for Exchange 

This MVP-recommended software scans the corrupt EDB files and recovers all the mailbox items, thus resolving the database consistency check failures in Exchange Server. It leverages advanced algorithms to extract data from corrupt Exchange database files. The tool then exports the extracted content to a PST file. Therefore, it sets you free from worrying about data loss despite backup failure resulting from EDB consistency check failure.

It is simple to install and use with an easy-to-understand UI. While using Eseutil requires high technical acumen, this professional exchange recovery tool is user-friendly and needs only a few clicks to operate. Besides its effectiveness in fixing the Exchange database consistency check failures, it is equally useful in resolving several critical case scenarios, such as: 

• The Exchange database is in a Dirty Shutdown state
• The Exchange server database encounters the issue of 'Failed Error: Couldn't mount the specified database.
• The Exchange server suffers a crash, leading to a failed database recovery

Key features of Stellar Repair for Exchange

• Advanced scanning algorithms to retrieve mailbox items from corrupt EDB files
• Recover mailboxes from ransomware-affected databases  
• Export the mailboxes directly to Office 365 or Live Exchange Server
• Recovers accidentally or intentionally deleted mailboxes and emails
• Repairs damaged or corrupt archive mailboxes and saves them to PST and other formats
• Advanced filter items to include or exclude selected email items
• Repairs corrupt public folders stored in the EDB File
• Repairs large EDB files quickly and effectively
• Recovers a dismounted EDB file on a virtual machine
• Create and review the log report after finishing the Exchange recovery

Conclusion

Windows Server Backup (WSB) is a widely used technique to back up Exchange Server. It ensures prompt recovery of the database in case it suffers damage or corruption. Often, even WSB may face the Exchange consistency check failure. Getting this error will signify EDB file corruption, causing a failed backup and turning it useless for recovery. 

This failure results mainly from compromised EDB files or missing log files. Besides, any issue with Volume Shadow Copy Service (VSS) writers can also cause this inconsistency. To resolve this error, you may try Eseutil, the built-in utility from Microsoft. 

However, it is likely to consume considerable time with less guarantee of successful recovery of the data. This can lead to loss of data and requires you to have in-depth technical knowledge. To overcome these limitations, using a professional exchange recovery tool will be a better option. This is where Stellar Repair for Exchange can prove helpful. 

Loaded with multiple features to repair and recover a corrupt Exchange server database, it holds widespread preference in small and large organizations.