As with the previous scenario in
which minimal data loss was the goal, proper naming conventions and cataloging are
a must.
Another key risk is the off-site storage. Where is it? Is it environmentally protected?
Is it secure? Keeping the backup tapes at someone??™s house is definitely a start and better
than nothing, but that has plenty of risks in and of itself. I once had a client whose twoyear-
old tried to jam a backup tape in a VCR.
Table 5-4 shows the risks inherent in this scenario.
Table 5-4. Risk Breakdown for a Flexible-Portability Scenario
Risk Worst-Case Impact Best-Case Impact
Data loss Possibly months??™ worth of data Almost zero data loss
Restore time A restore over every data file and all A single file restore, plus log files
of the log files
Perceived The length of a complete restore If the data file is in a filegroup that??™s
downtime accessed infrequently, possibly zero
perceived downtime
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 134
Scenario: Specific Tables Only
In SQL Server 6.5, you could back up and restore a single table. Once SQL Server 7.0 came
out, that functionality was removed.
Pages:
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273