Computer Associates SQLSTQ99000600 Microsoft SQL Guide - Page 129

Torn Repair Dependency Checklist

Get Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0 PDF manuals and user guides
UPC - 757943257441
View all Computer Associates SQLSTQ99000600 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 129 highlights

Restore Overview 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 Database Full Backup Prerequisites None For more information, see Note 2 (see page 130). Partial Full Backup None For more information, see Note 2 (see page 130). Files and FileGroups Full Backup None For more information, see Note 2 (see page 130). Database Differential Backup For more information, see Note 1 (see page 130). The last prior Database Full backup Partial Differential Backup For more information, see Note 1 (see page 130). Use the more recent of the following: ■ The last prior Database Full backup ■ The last prior Partial Full Post-requisites Use one of the following: ■ All successive Transaction log backups ■ All successive Transaction Log backups with Truncation and Transaction Log Tail backups Use one of the following: ■ All successive Transaction log backups ■ All successive Transaction Log backups with Truncation and Transaction Log Tail backups Use one of the following: ■ All successive Transaction Log backups ■ All successive Transaction Log backups with Truncation and Transaction Log Tail backups Use one of the following: ■ All successive Transaction Log backups ■ All successive Transaction Log backups with Truncation and Transaction Log Tail backups Use one of the following: ■ All successive Transaction Log backups ■ All successive Transaction Log backups with Truncation and Transaction Log Tail backups Appendix C: Backup and Recovery Best Practices 129

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
Restore Overview
Appendix C: Backup and Recovery Best Practices
129
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
(see page 130).
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
(see page 130).
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
(see page 130).
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
(see
page 130).
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
(see
page 130).
Use the more recent of the
following:
■
The last prior Database
Full backup
■
The last prior Partial Full
Use one of the following:
■
All successive Transaction Log backups
■
All successive Transaction Log backups
with Truncation and Transaction Log Tail
backups