You can use similar conventions as in the preceding list, but with logical naming,
simply remove the .bak extension. Most importantly, pick a naming convention and stick
to it as best you can. When disaster strikes, it can make a world of difference.
CHAPTER 2 n MAKING DATABASE BACKUPS 21
Backup Locations
Before you create a backup, you need to determine where the backup will go. Ultimately,
you only have two choices: TO DISK or TO TAPE. However, when it comes to disk, you have
a few different options to think about.
Local Disk
You can always specify a file when writing to disk. The syntax is quite simple:
BACKUP DATABASE AdventureWorks
TO FILE='D:\Data\AdventureWorks_Full.bak'
When backing up locally, you want to avoid placing the backup file on the same disk
array as the database itself. In the event of media failure, you??™d lose both the database
and the backup of the database. Note that I said disk array, not drive letter. It??™s possible
(and sometimes common) to have most of the local drive letters on the same physical
disk array.
nTip A common practice (and one I tend to favor) is backing up locally to disk, then copying the backup file
off to a network location or backing it up to tape.
Pages:
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