Warning AW51011

There are no known Torn Pages or Checksum Failures in the selected database. A Repair Restore cannot be performed.

Module

Agent for Microsoft SQL Server

Reason:

A “Torn Page Repair” restore is submitted for a database which is not actually damaged. When a Torn Page Repair restore is performed, the Agent for Microsoft SQL Server queries SQL Server for the list of damaged pages, and selects the damaged pages to be restored from the backup session. If there are no damaged pages, or if the damaged pages are all in data files which were not included in the selected backup session, or if SQL Server is not aware of the damaged pages, then this message will be posted, and the current backup session will be skipped.

Action:

If the database is in fact damaged, performing a Database Consistency Check (DBCC) will identify any damaged pages which SQL Server has not yet detected.

• If performing an Online Torn Page Repair, this can be done as part of the restore by selecting the Before Restore option under Database Consistency Check.
• If performing an Offline Torn Page Repair and the database is currently Online, then perform a Transaction Log Backup with the “Backup the Log Tail…” option to take the database Offline, and select the Before Backup option and Continue with Backup if DBCC Fails option under Database Consistency Check.
• If performing an Offline Torn Page Repair and the database is currently Offline in a Loading state, restore the last Transaction Log backup with the Leave Database Operational option and without the Automatic Dependency Selection option, and then perform a Transaction Log Tail backup as previously described.