() Error () during backup of a database (file ). The database will be unable to restore.

Details
Product: Exchange
Event ID: 217
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <number>Error (<error code>) during backup of a database (file <file name>). The database will be unable to restore.
   
Explanation

An error occurred during the online Exchange-aware backup of an Exchange Information Store database.

The cause for the online backup failure depends on the error listed in the Description section of the event. The most frequent causes are listed below.

  • This error may be generated because ESE was unable to gain exclusive access to the .pat file for the database. This file is created when the backup starts and it contains information about the changes that are made to specific pages while the backup is running. If pages are deleted during the backup after that part of the database has been written to tape, the .pat file holds the updated information. When the backup is completed, the .pat file is backed up and deleted. If the database goes offline during backup, the .pat file is not deleted until the next time backup starts and ESE deletes the current one and creates a new one.
  • Another cause relates to the -1018 error = JET_errReadVerifyFailure in the Description. This error indicates a hardware-related root cause. Check the system log, run chkdsk and perform other diagnostic tasks.
  • Another possible description relates to the -613 error. Error -613 translates to JET_errSLVReadVerifyFailure (checksum error in SLV file during backup, where “SLV” stands for “streaming” or “.stm” file). Error -613 may also be hardware related. Check the system log, run chkdsk and perform other diagnostic tasks. It is suspected that Error -613 may occur from non-hardware related issues such as different 3rd party SMTP disclaimer software packages.

Other causes are under investigation. If you have exhaustively checked all hardware-related causes, contact Microsoft Product Support Services.

   
User Action
  • If the .pat file is locked by another program such as antivirus or backup software, ESE will fail the backup. The resolution is to stop the other software or wait for it to finish accessing the .pat file. Perform another backup of the database.
  • If the Error in the description is -1018, to perform a successful backup, use one of the following methods. First determine the root cause of the failure and fix it — Error -1018 will return if the root cause is not fixed. Restore the information store from the previous online backup or if the mailbox store is affected and you have an Enterprise version of Exchange, move the mailboxes to another server or mailbox store. To repair the corruption in database pages if you do not have a valid backup and you are running the standard version of Exchange, run the eseutil /p command, and then run the isinteg -fix command on the affected store.

    CAUTION: After you make repairs to the database by using the eseutil /p switch, the database may not be stable and reliable. Because the repair process deletes database pages, data loss is likely.

    NOTE: If you must run a hard repair on your production database, Microsoft recommends that you move the data out of the repaired database to a new database, or rebuild the database using Move Mailbox or ExMerge.

  • If the Error in the description is -613, follow the resolution steps for Error -1018. NOTE: if the resolution requires a repair (as a last resort), you cannot repair the .stm file alone — you must repair the .edb file and its associated .stm file.

Related:

Leave a Reply