There are many items that are required in a Disaster Recovery (D/R) Plan, some are location specific but some are more generic. This article will touch on items critical for the success of the disaster recovery plan. Organizations may differ on the priority or of these items, but they must exist within the DR plan.
The most critical issue in the Plan is that it is current, and that a copy exits at the recovery site. You do not want to go through a recovery process with an outdated plan. The plan should detail the latest hardware and software configurations. Also the plan must be clearly laid out and easy to follow. A plan should not rival “War and Peace” in length or complexity. It should be concise with easy to follow bullet points. Though plans are written by individuals who anticipate their presence during the recovery, this cannot always be guaranteed. There may be issues that do not allow the plan’s author to be present during the recovery. Plans should be written so that someone with a similar skill level can accurately follow all steps in the plan. Omit any shorthand or technical jargon from instructions. It is important to realize that DR plans will probably be exercised under extreme conditions of stress and timing. When reviewing and editing the plan ask yourself “If I am trying to go through this at 2 AM after a full work day will I be able to understand what needs to be done?”
It is imperative that any DR plan have an accurate communication or call list. Some organizations utilize third party vendor products for this, regardless, the list must be current. The list should have designated backups for each key individual and multiple contact information for them as well. If you are using a call tree, make sure that you have a loop back so that the last person on the list will confirm that the call was made. Someone should be designated as the communication list manager to monitor responses and contact backup staff as necessary.
You must have and be able to work off a detailed script. There is no guarantee that the script will be followed by the same person who wrote it. For this and other reasons the script should have a formal review process by other members of the team. For best results use bullet points and easy to follow steps. When in a real recovery scenario, there will be intense pressure and many things going on at the same time. Add to this the possibility at it is to be executed at 2 AM the likelihood of confusion is high. Whatever can be done in the plan to make the steps easier to follow will go a long way. If at all possible, try to anticipate errors and include remediation steps. For example: “Connect network cable to PC.” If network not found, first check if PC Ethernet connection shows signal. Something as simple as that, when you are under extreme stress and fatigue goes a long way. Within the script keep things simple. Avoid using terms that may not be understood when extreme fatigue hits. If you must use technical terms that may not be understood, add a glossary of terms.
Once you have a detailed plan, you need to test and retest the plan. It is possible to test separate portions of the plan on their own, but make sure the whole plan is tested at least once a year OR if a major change takes place. Exercising or testing the plan often will make staff familiar with the plan. Try to exercise the plan with different staff members if you can. DO NOT assume anything in the plan, not even that everyone can make it to the recovery location at the correct time. When testing the plan try to anticipate unusual conditions. What would the team do if a drive or a technical component fails?
Each member of the team should be familiar with their defined role. Additionally the backup members must be familiar with their roles. If a team member whose primary role is applications has a backup role as a telecommunications resource, make sure they know what that role entails.
This next item may sound odd as a “Must Have” but believe me it is of utmost importance sometime. Have a list of restaurants and 24 hour supply delivery resources at the recovery site. You will likely spend many hours at a recovery site and will need to replenish supplies. You do not want to start searching for places when every minute and resource counts. You may very well need to be at the recovery site for longer than 24 hours at a time.
Part of the Disaster Recovery plan must include an application list. Each entry in the list should have the application name as the technical staff identifies it, the name the business side recognizes and any technical details such as server name etc. Along with the technical items, include the application owner, their full contact information and backup contacts.
There should be an accurate, that is, up to date, network diagram of the entire network as well as the recovery site. Each node on the switch and panels should have some means of identification. This will ease any issues with following cables and wires.
The DR Plan should contain an easy to follow map and directions of how to reach the recovery area. Secondary directions could be included as well, if the main route is congested or impassable for whatever reason. If there may be an issue with parking, you should specify additional parking facilities in the vicinity.
Additional documentation that is helpful within a DR plan is a list of vendor contacts and any applicable insurance documentation such as policy numbers. Another item that is helpful is a list of all the hardware and software licenses you may have.
Last week’s Quiz Question
What was the only major Revolutionary War Battle fought on Vermont soil?
Answer: The Battle of Hubbardton (http://en.wikipedia.org/wiki/Battle_of_Hubbardton)
Winner: Andrey N. Chernyaev
This week’s Quiz Question
The first guiding value of Norwich University is that “We are men and women of honor and integrity. We shall not tolerate those who ________________.
Current competition standings:
Andrey N. Chernyaev: 5 wins Matt Bambrick: 3 wins |
Dianne Tarpy: 2 wins |
Sam Moore |
Autumn Crossett |
Gil Varney, Jr. |
Glen Calvo |
Thomas Reardon |
Sherryl Fraser |
Srinivas Chandrasekar |
Marc Ariano |
Linda Rosa |
Joanna D'Aquanni |
Bill Lampe |
Srinivas Bedre Christian Sandy Joseph Puchalski Scott Madden Ken Desforges |
