Exchange Database Consistency Check – Fix the Error Instantly
Backup and recovery are essential activities of organizations who want to safeguard their data from data loss, virus attacks, or other disasters. Without a proper backup, your data is extremely vulnerable, and recovering from an impending failure may be nearly impossible. The same principle holds true for users who rely on Microsoft Exchange server for email storage, exchange, communication, and relaying. It contains thousands of user mailboxes, attachments, and important files, and there is no doubt that backup is given such a prominence. The Windows Server operating system includes a native utility called Windows Server Backup (WSB) that can be used to backup an Exchange server . Now that we understand why backup is important and how an Exchange server backup is performed, we will look at a common error that users encounter when performing backups and how to resolve the problem.
What causes the error 'Exchange Database Consistency Check Failed'?
This error occurs when the Windows Server backup utility fails to successfully perform a database consistency check due to a corrupted EDB or missing transaction log files, and it indicates that a successful backup of the Exchange server cannot be taken. The WSB first checks and compares the entire database with the log files that are being backed up to ensure that the information is up to date. It displays the error if there are inconsistencies or if the database is not consistent with the log files.
It is possible to skip this consistency check while performing the backup, but if the database is inconsistent or corrupted, you will be unable to successfully restore it to recover your data. The error displayed is usually 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'
