Disaster Recovery Planning... Been there. Done that. Not as hard as it looks. The typical Sysadmin looks at Disaster Revover from a System's point of view. You need to pull back on that approach and away from looking at each system. Disaster Recovery is more a state of mind. You need to examine (and document) your companies business flow, and then outline how you would bring that business flow back online. This does involve machines and applications, but it goes much further than that. Some key elements: - Copies of Insurance documents and policies at a known off-site facility. This would include an outline of your various policies and what they cover, as well as contact information and pre-filled out forms for making claims. You might also include current inventories (and a yearly projected inventory) for use as proof of insurance value. - Copies of Banking and finance documents at the same, known, off-site facility. This includes Bank account numbers, lines of credit, and access procedures. You will also need forms for granting access to surviving (or new) corporate personnel, and the procedure for granting them access approval (normally an emergency vote by the Board - so you'll need current contact information for all board members) - List of Board members and Corporate advisers and their contact information (phone numbers preferable). - Employee lists and their home/emergency contact information. - Contact information for current internet, network, and phone vendors. With this you will need to include an overview of each account, how they function, who to contact, and all the account numbers. You will also need a current list of all major published phone numbers, email addresses (the domains), and websites. These will need to be redirected quickly - so you will need a special section laying out the redirection of these resources. If you don't have multiple corporate locations, it helps to have a signed reciprocal agreement with another local corporation for emergency access to their phone and internet services (plus a room or two that can be converted for your use in an emergency). Failing that, you should have a list of local vendors who rent office space (complete with phone and internet access. - You will want to have pre-filled out forms ready to redirect your primary phone numbers to the new locations phone service. And procedures for having your internet web addresses redirected to a hosting service. - Your published emergency procedures will indicate that folks are to call the main number for information in case of a disaster. Stress that the main number may be down for a day but that procedures are in place to roll the number over to a new location as soon as possible - that location could even be somebody's home or a corporate Cell phone. - Contact numbers for various local Hardware/Software vendors and estimates of replacement costs/times for each departments inventory (desks/chairs/office supplies/computers/printers/software/training). - Procedures for bringing up key business systems. This will involve on-going backup and recovery procedures and off-site storage of vital corporate data (and intellectual property like source code and patent information). As part of this you will need to have as much of the recovery process laid out and completed as possible. That may include copies of your Backup software, as well as copies of all your installation software (with instructions for re-installing it) as well as copies of your licensing agreements and contracts. I hope that is a good overview of the procedures that need to be put in place. The folks at my former (and current) employ seemed to like it. Jon