Introducing Arcserve Backup Agents and Options › Using Agents › Agent for Microsoft SQL Server › Perform an Online Torn Page Restore Using Microsoft SQL Server 2000, 2005, 2008, 2012 or 2014 Enterprise, Data Center, or Developer Editions

Perform an Online Torn Page Restore Using Microsoft SQL Server 2000, 2005, 2008, 2012 or 2014 Enterprise, Data Center, or Developer Editions

Microsoft SQL Server 2000, 2005, 2008, 2012 and 2014 have the ability to detect when the data in the database has been damaged, and isolate the damage at the data page level. At any point in time, the current list of known damaged pages can be found in the [suspect_pages] table of system database [msdb]. In addition to torn page detection and isolation, SQL 2005 also introduces the ability to perform a Restore in which only those data pages which are damaged are overwritten. This will allow you to bring a database which is slightly damaged back into service quickly.

Note: Do NOT take the database offline before you start this procedure.

Follow these steps:

1. Change to Full Recovery Model, if the database is using the Simple Recovery Model.
2. (Optional) Perform a Database Consistency Check (DBCC CheckDB) on the database to locate any additional damaged pages beyond the one already reported. This can be done as part of step 4.
3. Perform an Online Torn Page Repair Restore of the database as follows:
   1. Open the Restore Manager.
   2. On the Source tab, use the Restore By Tree view to find and select the database.
   3. Open Agent Option.
   4. Confirm that Automatic Selection is selected.
   5. Under Subset, select Torn Page Repair – Online.
   6. Under Recovery Completion State, select Leave database operational.
   7. (Optional) You may select a Database Consistency Check before the restore, to identify any other damaged or corrupted pages. (Note that this is the only restore type for which a DBCC is permitted before a Restore, because DBCC requires the database to be online.)
   8. (Optional) You may select a Database Consistency Check after the restore.
   9. Click OK.
   10. On the Destination tab, select Restore to Original Location, if it is not selected.
   11. Start the Restore.
4. Attempt to query the table that contained the damaged page.
5. Perform a Transaction Log backup with the default options.
6. Perform a restore of this final Transaction Log backup without Automatic Selection, and with the Recovery Completion State set to Leave Database operational.
7. Change to Simple Recovery Model, if you changed the Recovery Model in step 1.
8. Resume use of the database.