Most IT departments are doing all they can
just to keep their heads above water, so any new undertaking is often frowned upon.
You need to plan for disaster recovery, even if you can only take a small step, and you
need to keep refining what you do. Disaster recovery is part of your job as a DBA. Don??™t
forget these tips:
??? Rinse and repeat: Disaster recovery planning needs to be an iterative process. It??™s a
job responsibility, not a project to complete.
??? Understand that every disaster is a learning opportunity in disguise: Every time
you face a disaster, take something from it. No one can think of every situation in
advance. It??™s when things truly go wrong that you really learn something.
??? Differentiate between mitigation and response: Sometimes it??™s unclear whether
you??™re dealing with mitigation or response. Clarify what you??™re working on. Mitigation
is prevention; response is reaction.
??? Remember that response plans are not optional: Some experts advocate spending
a great deal of time working with mitigation planning. They say that if you can
effectively prevent the problem from occurring, there??™s no need to come up with
a response plan.
Pages:
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542