Defining Mitigation Plans
While a response plan is required for every disaster, a mitigation plan is optional. However,
you??™re better off if you can prevent a disaster or minimize the impact then have to
react to it. Think of mitigation planning as proactive disaster recovery. However, you cannot
skip response planning and rely on mitigation plans. (Well, you could, but I certainly
wouldn??™t approve, and you??™re just asking for trouble.)
Since we??™re focusing on SQL Server disaster recovery, you essentially have a single
response plan for any disaster situation: a backup/recovery plan. With mitigation plans,
however, you can have a wide variety of plans given the type of disaster. Clustering is
good for addressing hardware disasters. Log shipping and database mirroring are prime
candidates for dealing with environmental, hardware, and media disasters. A database
snapshot is an excellent tool for dealing with process errors and can prove useful for
some user-based errors. However, no specific technology provides mitigation for all disaster
categories, much less for all specific disasters you could imagine.
Pages:
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504