SQL Server Backup and Restore - Simple Talk

More documents

Recommendations

Info

File Restore Chapter 9: File and Filegroup Backup and Restore In all previous chapters, when we performed a restore operation, we restored the database as a whole, including all the data in all the files and filegroups, from the full database backup, plus any subsequent differential database backups. If we then wished to roll forward the database, we could do so by applying the full chain of transaction log backups. However, it is also possible to restore a database from a set individual file backups; the big difference is that that we can't restore a database just from the latest set of full (plus differential) file backups. We must also apply the full set of accompanying transaction log backups, up to and including the log backup taken after the final file backup in the set. This is the only way SQL Server can guarantee that it can restore the database to a consistent state. Consider, for example, a simple case of a database comprising three data files, each in a separate filegroup and where FG1_1, FG2_1, FG3_1 are full files backups of each separate filegroup, as shown in Figure 9-4. Figure 9-4: A series of full file and transaction log backups. 318
Chapter 9: File and Filegroup Backup and Restore Notice that the three file backups are taken at different times. In order to restore this database, using backups shown, we have to restore the FG1_1, FG2_1 and FG3_1 file backups, and then the chain of log backups 1–5. Generally speaking, we need the chain of log files starting directly after the oldest full file backup in the set, and finishing with the one taken directly after the most recent full file backup. Note that even if we are absolutely certain that in Log5 no further transactions were recorded against any of the three filegroups, SQL Server will not trust us on this and requires this log backup file to be processed in order to guarantee that any changes recorded in Log5 that were made to any of the data files, up to the point the FG3_1 backup completed, are represented in the restore, and so the database has transactional consistency. We can also perform point-in-time restores, to a point within the log file taken after all of the current set of file backups; in Figure 9-4, this would be to some point in time within the Log5 backup. If we wished to restore to a point in time within, say, Log4, we'd need to restore the backup for filegroup 3 taken before the one shown in Figure 9-4 (let's call it FG3_0), followed by FG1_1 and FG2_1, and then the chain of logs, starting with the one taken straight after FG3_0 and ending with Log4. This also explains why Microsoft recommends taking an initial full database backup and starting the log backup chain before taking the first full file backup. If we imagine that FG1_1, FG2_1 and FG3_1 file backups were the first-ever full file backups for this database, and that they were taken on Monday, Wednesday and Friday, then we'd have no restore capability in that first week, till the FG3_1 and Log5 backups were completed. It's possible, in some circumstances, to restore a database by restoring only a single file backup (plus required log backups), rather than the whole set of files that comprise the database. This sort of restore is possible as long as you've got a database composed of several data files or filegroups, regardless of whether you're taking database or file backups; as long as you've also got the required set of log backups, it's possible to restore a single file from a database backup. 319
Page 1 and 2:
The Red Gate Guide SQL Server Backu
Page 3 and 4:
Copyright April 2012 ISBN 978-1-906
Page 5 and 6:
Maintenance plan backups __________
Page 7 and 8:
Preparing for Log Backups _________
Page 9 and 10:
Log Backups _______________________
Page 11 and 12:
About the author Shawn McGehee Shaw
Page 13 and 14:
Introduction jobs scheduled to back
Page 15 and 16:
Introduction backups, to file and e
Page 17 and 18:
Introduction • Chapters 5 and 6 c
Page 19 and 20:
Chapter 1: Basics of Backup and Res
Page 21 and 22:
The primary data file will contain:
Page 23 and 24:
CREATE TABLE TableName ( ColumnDefi
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Simple Chapter 1: Basics of Backup
Page 43 and 44:
Full Chapter 1: Basics of Backup an
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Summary Chapter 1: Basics of Backup
Page 51 and 52:
Chapter 2: Planning, Storage and Do
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Tape Chapter 2: Planning, Storage a
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Verifying restores Chapter 2: Plann
Page 79 and 80:
Log File Information • Physical F
Page 81 and 82:
Page 83 and 84:
Summary Chapter 2: Planning, Storag
Page 85 and 86:
Chapter 3: Full Database Backups It
Page 87 and 88:
Chapter 3: Full Database Backups su
Page 89 and 90:
Chapter 3: Full Database Backups CR
Page 91 and 92:
Chapter 3: Full Database Backups In
Page 93 and 94:
Chapter 3: Full Database Backups
Page 95 and 96:
Chapter 3: Full Database Backups No
Page 97 and 98:
Chapter 3: Full Database Backups Al
Page 99 and 100:
Figure 3-4: Back Up Database wizard
Page 101 and 102:
Chapter 3: Full Database Backups As
Page 103 and 104:
Chapter 3: Full Database Backups Th
Page 105 and 106:
Chapter 3: Full Database Backups at
Page 107 and 108:
Page 109 and 110:
Chapter 3: Full Database Backups
Page 111 and 112:
Chapter 3: Full Database Backups Fi
Page 113 and 114:
Page 115 and 116:
Chapter 3: Full Database Backups In
Page 117 and 118:
Chapter 4: Restoring From Full Back
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Figure 4-1: Getting SSMS prepared f
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Chapter 5: Log Backups A Brief Peek
Page 147 and 148:
Chapter 5: Log Backups Therefore, w
Page 149 and 150:
Chapter 5: Log Backups However, the
Page 151 and 152:
Chapter 5: Log Backups At the point
Page 153 and 154:
Chapter 5: Log Backups If it's a da
Page 155 and 156:
Chapter 5: Log Backups However, use
Page 157 and 158:
Chapter 5: Log Backups Creating and
Page 159 and 160:
Backup Stage Log Size Space Used Be
Page 161 and 162:
Taking Log Backups Chapter 5: Log B
Page 163 and 164:
Chapter 5: Log Backups the default
Page 165 and 166:
Chapter 5: Log Backups Figure 5-7:
Page 167 and 168:
Chapter 5: Log Backups USE [Databas
Page 169 and 170:
Chapter 5: Log Backups Figure 5-9:
Page 171 and 172:
Chapter 5: Log Backups CREATE DATAB
Page 173 and 174:
Chapter 5: Log Backups As a log fil
Page 175 and 176:
Chapter 5: Log Backups There are se
Page 177 and 178:
Chapter 5: Log Backups Finally, bef
Page 179 and 180:
Chapter 5: Log Backups USE ForceFai
Page 181 and 182:
Summary Chapter 5: Log Backups This
Page 183 and 184:
Chapter 6: Log Restores Possible Is
Page 185 and 186:
Figure 6-1: Database backup timelin
Page 187 and 188:
Chapter 6: Log Restores If we do ne
Page 189 and 190:
Chapter 6: Log Restores Right-click
Page 191 and 192:
Chapter 6: Log Restores Figure 6-5:
Page 193 and 194:
Chapter 6: Log Restores Now switch
Page 195 and 196:
GUI-based point-in-time restore Cha
Page 197 and 198:
Chapter 6: Log Restores You'll noti
Page 199 and 200:
Chapter 6: Log Restores Aside from
Page 201 and 202:
Chapter 6: Log Restores DatabaseFor
Page 203 and 204:
Chapter 6: Log Restores restore and
Page 205 and 206:
Chapter 7: Differential Backup and
Page 207 and 208:
Page 209 and 210:
Reduced recovery times Chapter 7: D
Page 211 and 212:
Database migrations Chapter 7: Diff
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Summary Chapter 7: Differential Bac
Page 239 and 240:
Chapter 8: Database Backup and Rest
Page 241 and 242:
Full Backups Chapter 8: Database Ba
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268: Chapter 8: Database Backup and Rest
Page 295 and 296: Chapter 9: File and Filegroup Backu
Page 307 and 308: USE [master] GO Chapter 9: File and
Page 311 and 312: USE [DatabaseForFileBackups] GO Cha
Page 317: Chapter 9: File and Filegroup Backu
Page 339 and 340: USE [DatabaseForPartialRestore] GO
Page 345 and 346: USE [Master] GO Chapter 9: File and
Page 349 and 350: Why Partial Backups? Chapter 10: Pa
Page 351 and 352: Chapter 10: Partial Backup and Rest
Page 353 and 354: USE [DatabaseForPartialBackups] GO
Page 369 and 370:
Appendix A: SQL Backup Pro Installa
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
SQL Server and .NET Tools from Red
Page 383 and 384:
SQL Prompt Pro Write, edit, and exp
Page 385 and 386:
SQL Monitor SQL Server performance
Page 387 and 388:
SQL Toolbelt The essential SQL Serv
Page 389 and 390:
.NET Reflector ® Decompile, browse
Page 391:
Brad's Sure Guide to SQL Server Mai
show all

SQL Server Backup and Restore - Simple Talk

Create successful ePaper yourself

Delete template?

Save as template?