logo for it-outsourcing-adviser.com
Home
Disaster Recovery
Industries
Business Continuity
ITIL Insights
IT Outsourcing
News/Blog
Managed Services
Change Management
SAS 70 Savvy
About Us
Contact Us
Privacy Policy
Disclaimer
Site Map

Subscribe To Our Site News
XML RSS
Add to Google
Add to My Yahoo!
Add to My MSN
Subscribe with Bloglines
leftimage for it-outsourcing-adviser.com

Disaster Recovery Plan Example
Key Components And Basic Rules

Using a disaster recovery plan example, this page reveals the key elements of disaster planning.

It also covers a few important and basic rules about making and using a plan example for disaster recovery.

  1. This is NOT an IT project where once it's completed it is parked on a shelf somewhere. It MUST be made part of your normal planning activities.
  2. For the plan to be effective, it MUST be kept current and tested regularly.
  3. Your organization MUST ensure that critical operations can resume normal operations within a reasonable time frame.
  4. Very often it is the IT Manager who is responsible for putting together this plan. That's OK, but he MUST make certain he's not "a team of 1." Part of setting a disaster recovery plan example is to involve management and/or supervisory level people from each of the business areas of the company.
  5. You MUST distribute the plan among the team members and make certain you retrieve the previous version.
  6. Each revision MUST be clearly dated and include a revision number so there's no confusion as to which is the most current edition. Ideally a senior executive should sign it.
  7. Keep the document simple, well structured, well organized and easy to follow. If you make it a 100-page document, it WILL be shelved. No one will look at it much less read it, and forget about attempting to maintain it.

You may want to review our definition of disaster recovery page for further background on the subject of the disaster recovery plan example.

Phase 1 - Project Initiation

Click here to contact us with your questions and to request your free books and executive summary of them. Protect your business. Use best practices for IT outsourcing and supplier selection.
  • There needs to be a Steering Committee made up of the senior executives from each business area as well as IT management. It's their job to confirm the business risk and analysis, approve funding for the necessary resources, and sign off on the overall plan.
  • There needs to be a project committee that includes IT supervisory personnel as well as management/supervisory people from each business units. This group defines the business risks, impact and minimum time requirements for resuming normal business functions and it tests the disaster recovery plan.
  • As part of the disaster recovery plan example, you define the scope and schedules of the project, and you address any issues that will impact the delivery of this plan.

Phase 2 - General Requirements Definition

  • Develop a security assessment of your IT environment, including people access controls, security, network hardware and software, PCs and servers, application systems, development and maintenance procedures, database controls, system access controls, insurance, and so on.
  • Setting a good disaster recovery plan example enables you to improve existing disaster related prevention plans, and implement preventative measures where none existed.
  • Present your findings to the Steering Committee for approval and submit purchase requirements for recovery and maintenance software needed to support these revised plans.
  • Develop your plan's framework.

Phase 3 - Business Impact Analysis

  • The business units define the critical systems, processes and functions as well as the economic impact of these processes not being available over what time frames.
  • Present this analysis to the Steering committee for confirmation and approval of resources required to support those processes.

Phase 4 - Profile Of Recovery Requirements

  • This process identifies the resources necessary to support the business critical processes defined in phase 3. This includes hardware, software, communications facilities, PCs, people, outside vendors and locations.
  • These requirements should be defined as short, medium and long-term.
  • Steering committee approval of resources is acquired.

Phase 5 - Disaster Plan Development

  • Individual components and the recovery steps are defined and documented. This includes changes to use procedures, upgrading of IT operating procedures, meetings with vendors and contract signings.
  • Define the recovery team roles and responsibilities.

Phase 6 - Defining The Testing Plan

  • Establish testing goals, review alternative testing strategies.
  • Establish testing dates including ongoing testing dates.
  • Review who's involved in the testing process and how it impacts the business units.

Phase 7 - Tests And Plan Implementation

  • Structure and conduct the test, document and review the results.
  • Update the plan with necessary changes.
  • Report the results to the Steering committee.

Phase 8 - Establishing Maintenance Program

  • Establish dates for periodic plan reviews, follow on testing of updated processes, changes to personnel, and training of any new personnel.
  • Obtain Steering committee approval.

Are You an IT Manager Team of 1?

Here is some "real world" advice for a disaster recovery plan example when you're not able to get the executive commitment to establish a proper disaster recovery program in your company.

  • Involve your company's auditors to help pitch the need for this program, and also to get more details on the steps you need to take internally.
  • As you are responsible for the annual IT budget, you may not get approval to purchase some specific components needed to build a proper disaster recovery plan, but you can inflate the costs of some other projects that will enable you to "bury" the costs of some items you need to purchase.
  • You may not gain approval to buy the full backup generator needed for your environment, but you should be able to get approval to have the cabling installed that would connect your computer room to the outside wall of the building where a generator would be temporarily installed in case of an electrical disaster such as a hurricane or ice storm.
  • Meet with all business units to ensure you have the proper backups for all critical areas of the company's operations. Set a good disaster recovery plan example and have everyone buy into it.
  • Meet with fellow IT Managers to review your overall computer and production environments to see where you could possibly get access to computer facilities if you needed in an emergency.
  • Involve all your IT staff in building the plan, and run the tests with them. This is much better than not doing anything at all.
  • Invest in the time and expertise of an IT disaster recovery consultant to help review your environment and build the best plan that you can.

Get More Help From Us

Our offer of professional help is a serious one. First of all, you'll find that while the site information is exhaustive, it appears in a brief, easy-to-read, often bulleted, executive style.

You won't get bogged down in details while browsing this site, but we DO have extensive in-depth information for you if you want or need it. It's free and all you have to do is ask!

Start right now by going to the Contact Us page and completing the simple online form. You'll receive immediate access to two authoritative industry books, which our site sponsor will mail to you at no cost.

As a thank you for participating in our site, you'll also receive a bonus download of "15 Interview Questions To Ask IT Outsourcing Providers".

Return to the "IT Disaster Recovery Plan" page from
this "Disaster Recovery Plan Example" page.

© IT Outsourcing Adviser
Contact Us