An error occurred during the online Exchange-aware backup of an Exchange 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, then 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, then 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 in the Description section. 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 signifies a checksum error in the 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 third-party SMTP disclaimer software packages. Other causes are under investigation. If you have exhaustively checked all hardware-related causes, contact Microsoft Product Support Services.
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 error, to perform a successful backup, use one of the following methods. First, determine the root cause of the failure and fix it. 1018 errors will return if the root cause is not fixed. Restore the Exchange 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. After you make repairs to the database by using the eseutil /p command, 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. 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.
For more information about ESE event 217, see:
| Target | Microsoft.Exchange.Databases | ||
| Category | EventCollection | ||
| Enabled | True | ||
| Event_ID | 217 | ||
| Event Source | ESE | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Remotable | True | ||
| Alert Message |
| ||
| Event Log | Application |
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| EventDS | DataSource | Microsoft.Windows.EventProvider | Default |
| GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
Home
<Rule ID="An_error_occurred_during_backup_of_an_Exchange_store_database" Enabled="onEssentialMonitoring" Target="Exch2003Core!Microsoft.Exchange.Databases" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="EventDS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>.</ComputerName>
<LogName>Application</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>Channel</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Application</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>217</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>ESE</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertOwner>$Data/PublisherName$</AlertOwner>
<AlertMessageId>$MPElement[Name="An_error_occurred_during_backup_of_an_Exchange_store_database.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>