SQL Server Backup and Restore - Simple Talk

More documents

Recommendations

Info

Chapter 8: Database Backup and Restore with SQL Backup Pro test the email setting on each server occasionally, to guarantee that any failure alerts are getting through. Details of how to configure the email settings are in Appendix A. • @DatabaseList – A comma delimited text list that contains the names of any databases that we want to back up. SQL Backup allows you to back up any number of databases at one time with a single command. When backing up every database on a server, we can simply omit this parameter from the script and, in the BACKUP command, replace [' + @DatabaseList + '] with [*]. • @BackupType – Used to determine what type of database backup will be taken. In this script there are three choices for this variable to take; full, log, and differential. In the next section of the script, we build the BACKUP commands, using the variables for which we have just configured values. We store the BACKUP command in the @SQLBackupCommand variable, until we are ready to execute it. Notice that a simple CASE statement is used to determine the type of backup operation to be performed, according to the value stored in @BackupType. We don't need to modify anything in this section of the script, unless making changes to the other settings being used in the BACKUP command, such as the compression level. Of course, we could also turn those into configurable parameters. The next section of the script is where we execute our BACKUP command, storing the ExitCode and ErrorCode output parameters in our defined variables, where: • ExitCode is the output value from the SQL Backup extended stored procedure. Any number above 0 indicates some sort of issue with the backup execution. • ExitCode >= 500 indicates a serious problem with at least one of the backup files and will need to investigate further. • ExitCode < 500 is just a warning code. The backup operation itself may have run successfully, but there was some issue that was not critical enough to cause the entire operation to fail. 266
Chapter 8: Database Backup and Restore with SQL Backup Pro • ErrorCode is the SQL Server return value. A value above 0 is returned only when SQL Server itself runs into an issue. Having an error code returned from SQL Server almost always guarantees a critical error for the entire operation. We test the value of each of these codes and, if a serious problem has occurred, we raise an error to SQL Server so that, if this were run in a SQL Server Agent job, it would guarantee to fail and alert someone, if the job were configured to do so. We do have it set up to send email from SQL Backup on a failure, but also having the SQL Agent job alert on failure is a nice safeguard to have in place. What we do in this section is totally customizable and dictated by our needs. Restoring Database Backups with SQL Backup Pro Having performed our range of full, log and differential backups, using SQL Backup, it's time to demonstrate several useful restore examples, namely: • restoring to the end of a given transaction log • a complete restore, including restores of the tail log backup • a restore to a particular point in time within a transaction log file. Preparing for restore In order to prepare for our restore operations, we're going to add a few new rows to MessageTable1, perform a log backup, and then add a few new rows to MessageTable2, as shown in Listing 8-10. 267
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: Chapter 7: Differential Backup and
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 265: 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 and 318:
Chapter 9: File and Filegroup Backu
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
USE [DatabaseForPartialRestore] GO
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
USE [Master] GO Chapter 9: File and
Page 347 and 348:
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 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
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?