Computer Associates SQLSTQ99000600 Microsoft SQL Guide - Page 123

Restore Overview, Appendix C: Backup and Recovery Best Practices

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

Restore Overview Note: When using the Simple Recovery Model, you cannot perform a Database Differential backup after a Partial Full backup, until you first perform another Database Full backup. For all recovery models, if you perform a Partial Full backup after a Database Differential backup, the Partial Full backup will be dependent on the Database Differential backup as a pre-requisite. Important! In SQL Server 7.0 and 2000, a Database Differential backup is dependent on any Files and FileGroup backups that might be between it and the previous Database Full backup. However, in SQL Server 2005 and later, a Database Differential or Partial Differential backup is dependent on any intervening Full backups, including Files and FileGroups Full and Partial Full backups. The Automatic Selection feature cannot detect this condition. If you mix Files and FileGroup backups with Database Differential and Partial Differential backups in SQL Server 2005, you may need to assemble the restore sequences manually. Restore Overview To restore is to load a database from a backup of that database and (if applicable) one or more backups of its Transaction log. If a database is lost or damaged, you can restore the database by reloading the most recent database backup and the successive log backups. A restore overwrites any information in the database with the backed up information. Use CA ARCserve Backup and the Agent for Microsoft SQL Server to perform restore operations using the Microsoft SQL Server Restore statement. When you restore a database that is live and online, Microsoft SQL Server rolls back any uncommitted transactions that were active at the moment the restore job began. When the restore operation is complete, the database is in the same state it was in when the Backup statement for the backup used in the restore job was initiated, excluding any transactions that were active at that point. As the data from the backup is being restored, Microsoft SQL Server reinitializes any remaining unused pages. For example, if a 100 MB database contains only 5 MB of data, Microsoft SQL Server rewrites all 100 MB of space. Consequently, it takes at least as long to restore a database as it does to create a database. Appendix C: Backup and Recovery Best Practices 123

  • 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
123
Note:
When using the Simple Recovery Model, you cannot perform a Database
Differential backup after a Partial Full backup, until you first perform another
Database Full backup. For all recovery models, if you perform a Partial Full
backup after a Database Differential backup, the Partial Full backup will be
dependent on the Database Differential backup as a pre-requisite.
Important!
In SQL Server 7.0 and 2000, a Database Differential backup is
dependent on any Files and FileGroup backups that might be between it and the
previous Database Full backup. However, in SQL Server 2005 and later, a
Database Differential or Partial Differential backup is dependent on any
intervening Full backups, including Files and FileGroups Full and Partial Full
backups. The Automatic Selection feature cannot detect this condition. If you
mix Files and FileGroup backups with Database Differential and Partial
Differential backups in SQL Server 2005, you may need to assemble the restore
sequences manually.
Restore Overview
To
restore
is to load a database from a backup of that database and (if
applicable) one or more backups of its Transaction log. If a database is lost or
damaged, you can restore the database by reloading the most recent database
backup and the successive log backups. A restore overwrites any information in
the database with the backed up information. Use CA ARCserve Backup and the
Agent for Microsoft SQL Server to perform restore operations using the Microsoft
SQL Server Restore statement.
When you restore a database that is live and online, Microsoft SQL Server rolls
back any uncommitted transactions that were active at the moment the restore
job began. When the restore operation is complete, the database is in the same
state it was in when the Backup statement for the backup used in the restore job
was initiated, excluding any transactions that were active at that point.
As the data from the backup is being restored, Microsoft SQL Server reinitializes
any remaining unused pages. For example, if a 100 MB database contains only 5
MB of data, Microsoft SQL Server rewrites all 100 MB of space. Consequently, it
takes at least as long to restore a database as it does to create a database.