Table 5-1 shows what a risk breakdown might
look like for a fast backup scenario.
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 127
Table 5-1. Risk Breakdown for a Fast-Backup Scenario
Risk Worst-Case Impact Best-Case Impact
Data loss Data lost to the last full backup Data lost only at the point of failure
Restore time Last successful full backup plus Current full backup and no more than
all transaction log restores a day??™s worth of transaction logs
Perceived downtime Dependent on restore time Dependent on restore time
Scenario: Fast Restore Required
SQL Server 2005 places a great deal of focus on high availability. Essentially, availability is
the business driver behind a need for minimal restore time. Any system that is critical to
conducting business probably falls under this category, and systems needing as close to
24x7 availability as possible are quickly changing from the exception to the norm. However,
the fast-restore scenario encompasses more than 24x7 systems.
A system that is needed only three hours a day can be just as critical in its availability
as one that must be up continuously.
Pages:
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260