SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 86 | Next

James Luetkehoelter

"Pro SQL Server Disaster Recovery"


CHAPTER 2 n MAKING DATABASE BACKUPS 27
Full Backup
Regardless of the recovery mode used, you need to start with a full backup. Both log
backups and differential backups require a full backup to use as a starting reference
point. No backup scheme is complete without at least one full backup.
I ran into one situation where the only resolution was to restore to a specific point in
time. The client said, ???No problem. We keep six months??™ worth of backups on tape.??? It
turned out to be six months??™ worth of transaction log backups; there were no full backups
anywhere on tape. Explaining to the client that there was no way I could restore the
transaction logs was one of the most painful discussions I??™ve ever had as a consultant.
Creating a simple, full backup statement in T-SQL is intuitive:
BACKUP DATABASE AdventureWorks TO DISK = 'D:\data\AW.bak'
There is a very serious issue with this statement, however. The default behavior for
a backup command is to append to the existing file. If you use the previous statement
in a recurring job, the AW.bak file will continue to grow until it consumes all of the disk
space.


Pages:
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