For any backup technique to be valid, it must abide by the following guidelines:
??? The backups must be portable: If you can??™t move your backup from point A to B,
it won??™t do you much good if your original server is literally on fire (yes, I??™ve seen it
happen).
??? The backups must be securable: This can be as simple as placing a backup tape in a
safe. If your backup involves simply replicating the entire database to 4,000 laptops
used by sales staff, security becomes an issue.
??? The backups must be the result of a repeatable process: I??™ve witnessed some fairly
amazing recoveries using ???accidental??? backups. One example involved moving a
disk array that was attached to a development server to the failed production
server. It just so happened that production had been copied over to the development
environment the previous night, so there was very little data loss. In this
example, no repeatable process occurred??”just fortuitous timing.
13
C H A P T E R 2
These guidelines are achieved primarily by using SQL Server T-SQL backup commands,
which will be the focus of this chapter.
Pages:
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74