30.06.2013 Views

SQL Server Backup and Restore - Simple Talk

SQL Server Backup and Restore - Simple Talk

SQL Server Backup and Restore - Simple Talk

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 5: Log <strong>Backup</strong>s<br />

the default values. As discussed in Chapter 3, since we are only storing one log backup set<br />

per file, we do not need to worry about making sure backup sets expire at a given time.<br />

Storing multiple log backups would reduce the number of backup files that we need to<br />

manage, but it would cause that single file to grow considerably larger with each backup<br />

stored in it. We would also run the risk of losing more than just one backup if the file<br />

were to become corrupted or was lost.<br />

Figure 5-5: The <strong>Backup</strong> set section configuration for log backups.<br />

The final section of the configuration options is titled Destination, where we<br />

specify where to store the log backup file <strong>and</strong> what it will be called. If there is a file<br />

already selected for use, click the Remove button because we want to choose a fresh<br />

file <strong>and</strong> location.<br />

Now, click the Add button to bring up the backup destination selection window. Click<br />

the browse (…) button <strong>and</strong> navigate to our chosen backup file location (C:\<strong>SQL</strong><strong>Backup</strong>s\<br />

Chapter5) <strong>and</strong> enter the file name DatabaseForLog<strong>Backup</strong>s_Native_Log_1.trn at the<br />

bottom, as shown in Figure 5-6.<br />

163

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!