Computer Associates SQLSTQ99000600 Microsoft SQL Guide - Page 49

Files and FileGroups restore, Partial restore, Torn Repair, Restore Options

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 49 highlights

Restore Options Files and FileGroups restore Restores selected files and FileGroups. You can restore files and FileGroups from either a Files-and-FileGroups backup, Partial backup or Database backup. When restoring files or FileGroups, you must first restore from a Full backup session, then optionally from a differential session, followed by all of the Transaction log backup sessions performed after the Full or Differential backup. When you restore a file or FileGroup, you must apply the Transaction log to the database files immediately after the last file or FileGroup operation. Note: A Files and FileGroups restore must be applied to the original database or to a restored copy of the original database. Otherwise, the logs will not be applicable. Partial restore A partial restore always restores the primary FileGroup and any other FileGroups you specify as a new database. The result is a subset of the database. FileGroups that are not restored are marked as offline and are not accessible. Note: A database that is created using a Partial Restore may not be eligible for a Database backup, due to the unrestored FileGroups being offline. To resolve this condition, either restore the remaining FileGroups to the partially-restored database, or remove them from the database structure using the Microsoft SQL Server Enterprise Manager or Management Studio. Torn Page Repair Restores only the pages of data on disk which have been marked as damaged. SQL Server 2005 has the ability to isolate the 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 are similar to a Files and FileGroups restore. There are both Online and Offline versions of this operation. In an Online Torn Page Repair, the database remains online the entire time, and undamaged tables are still accessible. In an Offline Torn Page Repair, the database should be taken offline using a Log Tail backup before the restore is performed. Online Repair requires the Enterprise Edition of SQL Server. Note: Torn Page Repair restore must be applied to the original database, or to a restored copy of the original database. Otherwise, the data and logs will not be applicable. Important! When using Automatic Selection, you may be unable to restore a database to a different location on a disk (for example, to a different drive letter or directory path, or with a different file name) using backups from previous versions of CA ARCserve Backup or BrightStor® Enterprise Backup. For more information about restoring to a different location, see Restore to Alternative Disk Locations Using Automatic Selection. Chapter 4: Restoring Microsoft SQL Server Databases 49

  • 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 Options
Chapter 4: Restoring Microsoft SQL Server Databases
49
Files and FileGroups restore
Restores selected files and FileGroups. You can restore files and FileGroups
from either a Files-and-FileGroups backup, Partial backup or Database
backup. When restoring files or FileGroups, you must first restore from a Full
backup session, then optionally from a differential session, followed by all of
the Transaction log backup sessions performed after the Full or Differential
backup. When you restore a file or FileGroup, you must apply the
Transaction log to the database files immediately after the last file or
FileGroup operation.
Note:
A Files and FileGroups restore must be applied to the original
database or to a restored copy of the original database. Otherwise, the logs
will not be applicable.
Partial restore
A partial restore always restores the primary FileGroup and any other
FileGroups you specify as a new database. The result is a subset of the
database. FileGroups that are not restored are marked as offline and are not
accessible.
Note:
A database that is created using a Partial Restore may not be eligible
for a Database backup, due to the unrestored FileGroups being offline.
To
resolve this condition, either restore the remaining FileGroups to the
partially-restored database, or remove them from the database structure
using the Microsoft SQL Server Enterprise Manager or Management Studio.
Torn Page Repair
Restores only the pages of data on disk which have been marked as
damaged. SQL Server 2005 has the ability to isolate the 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 are similar to a Files and FileGroups restore.
There are both Online and Offline versions of this operation. In an Online
Torn Page Repair, the database remains online the entire time, and
undamaged tables are still accessible. In an Offline Torn Page Repair, the
database should be taken offline using a Log Tail backup before the restore
is performed. Online Repair requires the Enterprise Edition of SQL Server.
Note:
Torn Page Repair restore must be applied to the original database, or
to a restored copy of the original database. Otherwise, the data and logs will
not be applicable.
Important!
When using Automatic Selection, you may be unable to restore a
database to a different location on a disk (for example, to a different drive letter
or directory path, or with a different file name) using backups from previous
versions of CA ARCserve Backup or BrightStor
®
Enterprise Backup. For more
information about restoring to a different location, see Restore to Alternative
Disk Locations Using Automatic Selection.