Developing business recovery plans is a complex process involving research and analysis. The goal of these multifunction...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
documents is to get the organization operational as quickly as possible after a technology disruption. But information gleaned from their development can occasionally be used in other areas.
Typical business recovery plans include information useful for any period of time, such as:
- Employee and stakeholder contact lists;
- Emergency contact lists;
- Vendor lists;
- Utility company contacts;
- Instructions for performing recoveries;
- Instructions for performing DR tests;
- Roles and responsibilities of DR teams;
- Equipment lists; and
- Technical diagrams of systems, networks and other assets.
Two key components of business recovery plans are the business impact analysis and the risk analysis. The business impact analysis identifies the following:
- Critical business processes that need to be maintained;
- Technologies required to support those processes;
- Resources to support those technologies;
- Internal and external dependencies the technologies need to function;
- Vital records and documentation necessary to manage the technology; and
- Operational and financial impacts from a loss of the technology.
The risk analysis identifies internal and external risks and threats to the continued operation of the technology outlined in the business impact analysis. Data from the risk analysis helps to identify and prioritize situations that must be addressed to mitigate negative outcomes to the organization if a specific threat occurs.
Here are five suggestions for how to get even more mileage out of business recovery plans:
- Results of the business impact analysis could be used to identify opportunities for process improvement and ways technology can better support business processes.
- Results of the risk analysis could be used as part of a larger, company-wide risk analysis.
- Recovery instructions and other information contained in the plan could serve as an alternate source of documentation in case existing technical manuals are destroyed.
- The plan provides a single source of key contact information, reducing the need to search multiple sources for contact data.
- The plan could serve as a reference document for use in product planning, product design, service design and delivery, and other new business activities, ensuring that DR elements are factored into new business offerings.
A comprehensive guide to BC/DR planning
Five experts' DR plan necessities
Making the case for disaster recovery plans
Dig Deeper on Disaster recovery planning - management
Related Q&A from Paul Kirvan
When taking a hybrid disaster recovery approach -- using public and private components -- it's important to understand your requirements, assets and ...continue reading
If you're considering software-defined networking in your disaster recovery platform, define your DR requirements first. SDN can help support data ...continue reading
A call tree can be an important piece of disaster recovery planning. Follow these steps for call tree design and execution to ensure your company is ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.