Torn Page Repair Dependency Checklist

Backup and Recovery Best Practices › Restore Overview › Checklists for Dependencies, by Type › Torn Page Repair Dependency Checklist

Torn Page Repair Dependency Checklist

A Torn Page Restore restores only the pages of data on disk marked as damaged. SQL Server 2005 and later have the ability to isolate damaged parts of a database while leaving the rest intact. When this happens with a Full Recovery Model database, the database may be eligible for a Torn Page repair, which is much faster than a Database restore. The dependencies for this restore type are similar to those for a Files and FileGroups restore.

There are both Online and Offline versions of this operation.

Online -- The database remains online and undamaged tables are still accessible. This requires the Enterprise Edition of SQL Server.
Offline -- The database should be taken offline using a Log Tail backup before the restore is performed.

Selected Session	Prerequisites	Post-requisites
Database Full Backup	None For more information, see Note 2.	Use one of the following: All successive Transaction log backups All successive Transaction Log backups with Truncation and Transaction Log Tail backups
Partial Full Backup	None For more information, see Note 2.	Use one of the following: All successive Transaction log backups All successive Transaction Log backups with Truncation and Transaction Log Tail backups
Files and FileGroups Full Backup	None For more information, see Note 2.	Use one of the following: All successive Transaction Log backups All successive Transaction Log backups with Truncation and Transaction Log Tail backups
Database Differential Backup For more information, see Note 1.	The last prior Database Full backup	Use one of the following: All successive Transaction Log backups All successive Transaction Log backups with Truncation and Transaction Log Tail backups
Partial Differential Backup For more information, see Note 1.	Use the more recent of the following: The last prior Database Full backup The last prior Partial Full backup	Use one of the following: All successive Transaction Log backups All successive Transaction Log backups with Truncation and Transaction Log Tail backups
Files and FileGroups Differential Backup For more information, see Note 1.	The last prior Full Backup that contains the files included in the selected session	Use one of the following: All successive Transaction Log backups All successive Transaction Log backups with Truncation and Transaction Log Tail backups

Selected Session

Prerequisites

Post-requisites

Database Full Backup

None

For more information, see Note 2.

Use one of the following:

All successive Transaction log backups
All successive Transaction Log backups with Truncation and Transaction Log Tail backups

Partial Full Backup

None

For more information, see Note 2.

Use one of the following:

All successive Transaction log backups
All successive Transaction Log backups with Truncation and Transaction Log Tail backups

Files and FileGroups Full Backup

None

For more information, see Note 2.

Use one of the following:

All successive Transaction Log backups
All successive Transaction Log backups with Truncation and Transaction Log Tail backups

Database Differential Backup

For more information, see Note 1.

The last prior Database Full backup

Use one of the following:

All successive Transaction Log backups
All successive Transaction Log backups with Truncation and Transaction Log Tail backups

Partial Differential Backup

For more information, see Note 1.

Use the more recent of the following:

The last prior Database Full backup
The last prior Partial Full backup

Use one of the following:

All successive Transaction Log backups
All successive Transaction Log backups with Truncation and Transaction Log Tail backups

Files and FileGroups Differential Backup

For more information, see Note 1.

The last prior Full Backup that contains the files included in the selected session

Use one of the following:

All successive Transaction Log backups
All successive Transaction Log backups with Truncation and Transaction Log Tail backups

Note 1

In SQL Server 2005 and later, a Differential backup of any particular data file is dependent on the last prior Full backup of that data file. If a data file is contained in a Partial Full or Files-and-FileGroups Full backup, a Database Differential backup made after that Partial Full or Files-and-FileGroups backup and before the next Database Full backup will be dependent on that Partial Full or Files-and-FileGroups backup. The same applies to a data file included in a Files-and-FileGroups Full backup and a Partial Differential backup, or if the file selections vary between File-and-FileGroup Full and File-and-FileGroup Differential backups. Arcserve Backup does not detect these conditions in this release.

Alternatively, restoring Transaction Log backups that are between the Database Full or Partial Full backup and the Database or Partial Differential backup will serve to place the database in a correct state to restore from the Differential backup. However, this will take longer to execute than restoring the intervening Files-and-FileGroups Full or Partial Full backups.

Note 2: To perform a Files-and-FileGroups restore or an Offline Torn Page Repair, the database must be in a Loading or standby state. This is usually accomplished by performing a Transaction Log Tail backup but may also be accomplished by performing a Database restore of the selected session or older using the option, Leave database non-operational but able to restore additional transaction logs. However, if you restore an older session, you will need to restore all Transaction Log sessions between the older session and the selected session, or the Transaction Log restores after the Files-and-FileGroups restore will not be able to be applied to the other database files, and may fail.