Article ID: 2616952 - View products that this article applies to.
The Windows Server Backup may fail during the Exchange Consistency Check.
The application event log will record the following error:
Log Name: Application
Event ID: 517
Backup started at '8/25/2011 6:27:32 PM' failed with following error code '2155348010' (One of the backup files could not be created.). Please rerun backup once issue is resolved.
If you examine the application event log more you will notice errors similar to the following:
Log Name: Application
Event ID: 565
Consistency check for component '03ed71c2-8671-4a21-b15e-17159136543c'\'Microsoft Exchange Server\Microsoft Information Store\CONTOSOSERVER' failed. Application 'Exchange' will not be avaliable in the backup done at time '8/25/2011 12:27:32 PM'
When the server backup runs and does a backup of the volume containing the Exchange databases, the backup will perform a consistency check on the Exchange databases and the log files. If the consistency check fails because of a missing or corrupt log file or database then the backup job will fail and these errors will be logged.
We must first determine which logs or databases are affected. A standard Small Business Server contains two Exchange databases. We can use the Exchange ESEUTIL utility to check the consistency of the logs and the databases. We need to run ESEUTIL /K against each database and the log files.
On a default installation of Small Business Server 2008 there are two Exchange databases (the mailbox database and the public folder database). The mailbox database and the associated log files are by default located at c:\program files\microsoft\exchange server\mailbox\first storage group. The public folder store and its associated log files are located by default at c:\program files\microsoft\exchange server\mailbox\second storage group.
You would use the following steps to run a consistency check against the mailbox database:
1. Dismount the mailbox database
2. Open an Administrator command prompt
2. Change to c:\program files\microsoft\exchange server\mailbox\first storage group (if you have moved the database, the location will be different)
3. Run ESEUTIL /K E00 to verify the log files.
If any of the log files report an error, you can move the log files to a temporary location and remount the database and attempt the backup operation again.
4. Run ESEUTIL /K "mailbox database.edb" to verify the mailbox database.
A clean database will report zero checksum mismatches. If an error in the database is detected, you will need to either restore the database from a backup or perform a repair of the database file. For additional information of repairing an Exchange database, see http://technet.microsoft.com/en-us/library/aa997152(EXCHG.80).aspx
Here is an example of the output from a damaged database:
Initiating CHECKSUM mode...
Database: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\mailbox Database.edb
Temp. Database: TEMPCHKSUM8184.EDB
File: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storag
ERROR: page 150 checksum failed ( 0xac51ac51302fbea2 / 0xe9e8e9e82531bd59 )
Checksum Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
..................................................ERROR: page 20126 checksum failed ( 0xf432f4326dafd90d / 0xc6a2395dc22dfc7a )
ERROR: page 22102 checksum failed ( 0xafb0afb00331f36b / 0xbc75bc758c5f3b9c )
24066 pages seen
3 bad checksums
0 correctable checksums
294 uninitialized pages
0 wrong page numbers
0x546d56 highest dbtime (pgno 0x5907)
3009 reads performed
188 MB read
1 seconds taken
707113 milliseconds used
234 milliseconds per read
359 milliseconds for the slowest read
0 milliseconds for the fastest read
Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database fi
le or corrupted db) after 0.936 seconds.
In this example, the database has some logical corruption and it fails the consistency check. In order to recover from the corruption you must either restore the database from a backup or run a repair of the database. Once the corruption issue has been resolved, you can mount the database and try the backup operation again.
You need to repeat these steps for the public folder database and any other Exchange databases.
For additional information on the ESEUTIL /K command, see the following site: http://technet.microsoft.com/en-us/library/bb123956(EXCHG.80).aspx
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2616952 - Last Review: January 20, 2012 - Revision: 4.0