When you are finishing a backup on your Exchange 2000 computer, the
log files are not committed to the public or private information stores.
During the backup, the checkpoint file is still increased for each log
file that is filled. After the backup process completes, the logs are
committed to the information stores until they reach the highest number
recorded by the checkpoint file.
Fill out an exchange server request form
If the backup process stops responding, the checkpoint file continues
to increment for each log file that is filled. The checkpoint file continues
to increment until it reaches a maximum value of 1088. In Exchange 2000
Server Service Pack 2 (SP2) and earlier, this value is 256. After the
checkpoint file reaches the maximum value threshold, the information
store is dismounted. The following event is generated when the store
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 471
Computer: Server Name
Information Store (3420) Unable to rollback operation #65678740
on database C:\EXCHSRVR\mdbdata\priv1.edb.
Error: -614. All future database updates will be rejected. For more
information, click http://www.microsoft.com/contentredirect.asp.
The information store dismounts to prevent the checkpoint file from
becoming too far ahead of the transaction logs. This behavior can also
be used to determine if there are unresolved issues with your backup.
To mount stores that are affected by this behavior, first determine
the checkpoint value from the Exx.log file for the storage group that
is affected. To determine the checkpoint value, use the Eseutil utility.
After you have determined the checkpoint value, move the committed logs
to a backup folder.
Move the Edb.chk file from the log file folder, and then mount the stores.
Exchange now plays through the remaining uncommitted logs and permits
the store to mount.
This behavior is by design.
Call: 800-275-2823 or fill out a quote