Read time 4 min
For businesses, taking regular backups of their data is very crucial. Every organization, whether small or large, deals with massive amounts of data, and they cannot afford to lose this critical data. Therefore, organizations use different backup techniques to ensure their data is safe and secure.
One such a backup technique is Windows Server Backup. This feature provides backup & recovery options for every application in a Windows Server environment including Exchange Server.
But, even after being a useful tool to back up data, it can face problems sometimes, such as Exchange Consistency Check failure.
It is a process which is performed by Windows Server Backup application to ensure that the snapshot of the Exchange Database that is being backed up is valid and up-to-date. In simple words, we can say that it checks whether the backup of the database contains all the information or not. The Exchange consistency is checked by paralleling the contents of the database files with the information available in log files.
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:
Description: The backup started at “09/26/2018 5:22:45 PM” failed with the error code “2155348010.” Please rerun the backup once the error is resolved.
On examining the application event log, you’ll get some other errors like:
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.”
When you run server backup or do a backup for the Exchange Server, a consistency check will be performed on the Exchange databases and log files. But the consistency check occasionally fails due to a missing or corrupt database file or log files, and then the backup job will also fail.
To resolve this issue, first, you have to determine which logs or databases are affected. Once you find the affected database, you can use the in-built tool ESEutil to resolve the Exchange database consistency check issue. You’ll have to run ESEutil tool against each database and the log files to check 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.
This fix can be used in Windows Small Business Server 2011 Standard, Windows Small Business Server 2008 Standard, and Windows Small Business Server 2008 Premium.
After performing these steps if you find any error in the database, then you’ll either have to restore the database or perform a repair of the database file.
But, there is no guarantee that it will resolve the issue because it’s only ideal for fixing minor issues. Also, using ESEutil is a time-consuming process.
If you don’t have good backups, you may have to recover data from damaged EDB files. An Exchange Server recovery tool – Kernel for Exchange Server recovery is an advanced software that can be used to recover Exchange data. Using the Exchange Server Recovery tool, you can easily back up your Exchange mailboxes and save them to the desired location. Not only that, the smart filtering options of the tool allow users to back up specific data based on item type, date, exclude folders, etc.
This tool is enriched with some smart features that enhance the Exchange Server Recovery performance. Some of the extensive features are:
This tool can extract Exchange data from .bkf files created by Windows NT/Symantec/ Backup Files, .fd files created by HP Backup Files, and .ctf files created by CA ARCserve Backup Files.
Windows Server backup feature performs a consistency check on Exchange application during backup. Sometimes, this consistency check may show errors resulting in a failed Exchange backup. In most cases, you can fix this issue manually. However, if you don’t have good backups for Exchange data, you can recover Exchange data from the damaged files.