To minimize the likelihood of stress-related errors,
respond to the ???looking over your shoulder??? syndrome by having another set of (technical)
eyes watch what you??™re doing.
Given the proposed backup scheme (in Full Recovery mode), Table 5-2 shows what
the risk matrix would look like.
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 130
Table 5-2. Risk Breakdown for a Fast-Restore Scenario
Risk Worst-Case Impact Best-Case Impact
Data loss Data lost to the last good full backup Data lost since the last transaction log
and the associated differential backups backup
Restore time Mistakes made during restore require The time of a full backup restore, one
multiple attempts at a full backup restore differential restore, and a tail-log
restore
Perceived Restore time plus an application recon- Restore time only
downtime figuration required
Scenario:Minimal Loss Desired
Data means everything. Minimal data loss is usually mutually exclusive with the fastest
restore time possible.
nNote SQL Server 2005 is marketed as having ???Always On Technologies.??? It??™s true that there are some
fantastic improvements in the areas of high availability (some of which I??™ll cover in the next half of the book),
but that focus draws attention away from the backup/restore scenario in which minimal data loss is the
goal.
Pages:
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266