How to Solve "An error occurred during backup of an Exchange store database..." Error?
For the reason that Microsoft Exchange Server mainly acts as a mailbox server, backing up the database regularly is the key to deal with disaster recovery needs. Microsoft recommends using an Exchange-aware backup utility such as Windows Server 2003 backup or any third-party application. These utilities require access of.pat file (discussed in 'cause' section) and Exchange Server to be free from any hardware-related errors to successfully backup the database. At times, these hardware-related concerns also bring corruption to the database, which makes it obligatory either to restore from the last backup or perform Exchange Server Repair [http://www.ms-exchange-server-repair.com/] to repair EDB file of MS Exchange Server.
To apprehend such situations better, consider a scenario when you try to perform an Exchange-aware backup of the Exchange database. But due to some causes, the operation fails and you get an error message mentioned below:
"An error occurred during backup of an Exchange store database - the cause and resolution for the online backup failure depends on the error listed in the Description of the event."
This error is generated by ESE (Extensible Storage Engine) and is associated with event ID 217. The error statement further mentions another error in its description section that actually determines the root cause of failure.
Cause
General reasons causing the above behavior to occur are:
1. ESE cannot access the database.pat file exclusively. Exchange Server uses this file while backup is running to keep a record of updated pages, separately for both private and public stores. This is the patch file that ensures backing up of pages modified while backup is running.
2. If the description section of error reports -1018 error, this might be because of some hardware-related issues.
3. In case of description section mentioning -613 error, the cause could be checksum error in.stm (SLV) file. Another possibility is some hardware-related concerns.
Solution
You need to apply these measures to solve the described problem:
1. Another program might be accessing the.pat file, so either stop the software or wait till it finishes.
2. In case of -1018 error, find and solve the issue behind and restore the database from the last online backup if available. If you are using Enterprise edition, you can also use Exmerge. In other cases, you can perform EDB Repair using eseutil /p, followed by isinteg -fix commands, but the data loss is likely.
3. Follow the same steps as for -1018 error in case of -613 error. You need to repair.stm file along with the associated.edb file.
Since eseutil /p causes database pages to delete, it is more suggested to opt for third-party Exchange Server Repair utilities.
MS Exchange Repair Software is an advanced and reliable tool that repairs Exchange databases and restores the mailboxes as *.pst file. The Exchange Repair software supports MS Exchange Server 5.5, 2000, and 2003. The software is valid to use in each instance of database corruption with an interactive design and look.
To apprehend such situations better, consider a scenario when you try to perform an Exchange-aware backup of the Exchange database. But due to some causes, the operation fails and you get an error message mentioned below:
"An error occurred during backup of an Exchange store database - the cause and resolution for the online backup failure depends on the error listed in the Description of the event."
This error is generated by ESE (Extensible Storage Engine) and is associated with event ID 217. The error statement further mentions another error in its description section that actually determines the root cause of failure.
Cause
General reasons causing the above behavior to occur are:
1. ESE cannot access the database.pat file exclusively. Exchange Server uses this file while backup is running to keep a record of updated pages, separately for both private and public stores. This is the patch file that ensures backing up of pages modified while backup is running.
2. If the description section of error reports -1018 error, this might be because of some hardware-related issues.
3. In case of description section mentioning -613 error, the cause could be checksum error in.stm (SLV) file. Another possibility is some hardware-related concerns.
Solution
You need to apply these measures to solve the described problem:
1. Another program might be accessing the.pat file, so either stop the software or wait till it finishes.
2. In case of -1018 error, find and solve the issue behind and restore the database from the last online backup if available. If you are using Enterprise edition, you can also use Exmerge. In other cases, you can perform EDB Repair using eseutil /p, followed by isinteg -fix commands, but the data loss is likely.
3. Follow the same steps as for -1018 error in case of -613 error. You need to repair.stm file along with the associated.edb file.
Since eseutil /p causes database pages to delete, it is more suggested to opt for third-party Exchange Server Repair utilities.
MS Exchange Repair Software is an advanced and reliable tool that repairs Exchange databases and restores the mailboxes as *.pst file. The Exchange Repair software supports MS Exchange Server 5.5, 2000, and 2003. The software is valid to use in each instance of database corruption with an interactive design and look.
