Nothing (other than a backup) is more helpful during an emergency than a well-thought-out recovery plan. Actually, this is an overall term because you should plan for network or server outagesfrom the loss of a single disk drive to the loss of a single computer system, and even to the loss of your entire network. Chapter 3, "Network Design Strategies," stresses that you should always document the network and its components. Recovery procedures should be part of this documentation. The problem with disasters is that you can't schedule them. They don't always occur during normal business hours when you are wide awake and functioning well. In the middle of the night after a long day at work, you might get called in to restore a system without having the advantage of a good night's sleep. A good disaster-recovery plan can be helpful if only to keep you from making a mistake during the recovery process. A good disaster recovery plan includes several items:
|