However, you need to discuss the simplest of
steps toward achieving those big-picture goals.
??? Document while doing: Yes, we all hate documentation, but it must be done. If
you??™re the sole DBA, a disaster can always occur. If there are multiple DBAs where
you work, they??™ll need to be familiar with what??™s being done. I??™m horrible with
documentation myself. I find that the best way to ensure documentation is to
continually write things down and never wait until after the fact to create the
documentation.
??? Assume nothing: I??™ll avoid any clich?© comments about this. The bottom line is that
a disaster recovery plan should include the most obvious of information. You never
know what information will be obvious to whom when the plan is needed.
nNote Don??™t be shy about stating the most obvious principles. They may seem intuitive to you, but the
same concept may mean something completely different to someone else. Just like everything else with
disaster recovery, expect the worst.
CHAPTER 11 n DISASTER RECOVERY PLANNING 270
Risk, Response, and Mitigation
As mentioned in Chapter 1, disaster recovery planning is a combination of preparing a
response in the event of a disaster and reducing the likelihood that a given disaster will
occur.
Pages:
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496