Close
  • Latest News
  • Big Data and Analytics
  • Cloud
  • Networking
  • Cybersecurity
  • Applications
  • IT Management
  • Storage
  • Sponsored
  • Mobile
  • Small Business
  • Development
  • Database
  • Servers
  • Android
  • Apple
  • Innovation
  • Blogs
  • PC Hardware
  • Reviews
  • Search Engines
  • Virtualization
Read Down
Sign in
Close
Welcome!Log into your account
Forgot your password?
Read Down
Password recovery
Recover your password
Close
Search
Menu
Search
  • Latest News
  • Big Data and Analytics
  • Cloud
  • Networking
  • Cybersecurity
  • Applications
  • IT Management
  • Storage
  • Sponsored
  • Mobile
  • Small Business
  • Development
  • Database
  • Servers
  • Android
  • Apple
  • Innovation
  • Blogs
  • PC Hardware
  • Reviews
  • Search Engines
  • Virtualization
More
    Home Latest News
    • Storage

    10 Essential Components of an Effective Disaster Recovery Plan

    By
    Chris Preimesberger
    -
    June 6, 2017
    Share
    Facebook
    Twitter
    Linkedin

      PrevNext

      110 Essential Components of an Effective Disaster Recovery Plan

      10 Essential Components of an Effective Disaster Recovery Plan

      Data is the lifeblood of any enterprise. However, backup and data recovery investments can be difficult to sell internally because their benefits aren’t readily apparent on the bottom line. Just like any insurance policy, these systems matter most when the unpredictable happens, such as a hurricane, fire, flood or cyber-attack. With data and cyber-security in the spotlight, enterprises of all sizes are taking a closer look at how to cope if and when a breach or other incident that impacts the business occurs. Having a well-designed disaster recovery (DR) plan can be the difference between bouncing back from an incident or going under. In this eWEEK slide show, Larry Novak, service manager for cloud recovery at ViaWest, highlights the key components an effective DR plan should have.

      2Plan Description and Overview

      Plan Description and Overview

      Your business should have a document that provides the scope of the plan, objectives and assumptions. This should identify the address and location of the production site and the recovery site and include maps and directions as necessary. It should also describe when to put the plan in motion. What are the triggers that would cause a disaster declaration and activation of the DR plan?

      3Recovery Strategy

      Recovery Strategy

      An overview of your recovery strategy should provide a brief description of the tools and methods to be used to recover critical systems. This includes not only the names and location of your backups, but also the procedure necessary to retrieve the backup files. 

      4Accurate, Up-to-Date Call Lists and Communication Plan

      Accurate and Up-to-Date Call Lists and Communication Plan

      Equally as important as your infrastructure are the people behind it. Your DR plan should list the members and their titles, telephone numbers and email addresses for the various teams involved in recovery, such as senior leadership; an authorized list of names who can declare a disaster; the recovery team; and the damage assessment team. The conference bridge line also should be included in the document.

      5Minimum Critical Infrastructure

      Minimum Critical Infrastructure

      Your plan should list the infrastructure that will be required at the recovery site in order to have fully functional and operational systems. This includes the equipment for firewalls, switches, routers, storage, LANs and internet connectivity. Also, provide a list of servers (and their configurations) for backup and restoration software, security and virtual host servers. Prioritized List of Critical Applications and Systems

      6Prioritized List of Critical Applications and Systems

      Prioritized List of Critical Applications and Systems

      Not all of your applications are business-critical. The DR plan should not only include a list of the applications and databases that should be recovered but also the sequence in which they should be restored. Expected Recovery Point Objective (RPO) and Recovery Time Objective (RTO), which can vary depending on your unique company needs, should be listed for each system. A list of the hardware required for each system should also be documented.

      7Runbooks

      Runbooks

      You don’t want to leave anyone scratching their heads during a disaster. A section of the plan should include detailed steps that the IT staff will follow to recover the infrastructure (based on your prioritized list) and applications and systems (based on your minimum critical infrastructure).

      8Detailed Script and Action Items

      Detailed Script and Action Items

      When the DR plan is activated, it should include a detailed script that can be followed and executed by the recovery team leader. The script should contain each of the tasks involved in a recovery, and who is responsible for performing those tasks.

      9Testing the DR Plan

      Testing the DR Plan

      The DR plan should contain a section that identifies how often the plan should be tested, as well as a list of dates that the plan was tested with a brief summary of the results, and a list of and/or links to any post-test documents and lessons learned. The steps necessary to “failback”—restore operations to a primary machine or facility after a DR test or actual disaster—should be identified.

      10Roles and Responsibilities

      Roles and Responsibilities

      Each member of the various teams involved in DR should be familiar with his or her defined role. A list of everyone involved in the recovery process should be included in your documentation, along with their role and responsibility. A secondary or backup person also should be listed for each member.

      11Network Diagram and Inventory List

      Network Diagram and Inventory List

      An inventory list of all of the equipment at the production site and the recovery site should be included in the plan.  A current, detailed diagram of the entire network—including circuit IDs—should also be part of the plan. 

      PrevNext

      MOST POPULAR ARTICLES

      Android

      Samsung Galaxy XCover Pro: Durability for Tough...

      Chris Preimesberger - December 5, 2020 0
      Have you ever dropped your phone, winced and felt the pain as it hit the sidewalk? Either the screen splintered like a windshield being...
      Read more
      Cloud

      Why Data Security Will Face Even Harsher...

      Chris Preimesberger - December 1, 2020 0
      Who would know more about details of the hacking process than an actual former career hacker? And who wants to understand all they can...
      Read more
      Cybersecurity

      How Veritas Is Shining a Light Into...

      eWEEK EDITORS - September 25, 2020 0
      Protecting data has always been one of the most important tasks in all of IT, yet as more companies become data companies at the...
      Read more
      Big Data and Analytics

      How NVIDIA A100 Station Brings Data Center...

      Zeus Kerravala - November 18, 2020 0
      There’s little debate that graphics processor unit manufacturer NVIDIA is the de facto standard when it comes to providing silicon to power machine learning...
      Read more
      Apple

      Why iPhone 12 Pro Makes Sense for...

      Wayne Rash - November 26, 2020 0
      If you’ve been watching the Apple commercials for the past three weeks, you already know what the company thinks will happen if you buy...
      Read more

      eWeek has the latest technology news and analysis, buying guides, and product reviews for IT professionals and technology buyers. The site’s focus is on innovative solutions and covering in-depth technical content. eWeek stays on the cutting edge of technology news and IT trends through interviews and expert analysis. Gain insight from top innovators and thought leaders in the fields of IT, business, enterprise software, startups, and more.

      Facebook
      Linkedin
      RSS
      Twitter
      Youtube

      Advertisers

      Advertise with TechnologyAdvice on eWeek and our other IT-focused platforms.

      Advertise with Us

      Menu

      • About eWeek
      • Subscribe to our Newsletter
      • Latest News

      Our Brands

      • Privacy Policy
      • Terms
      • About
      • Contact
      • Advertise
      • Sitemap
      • California – Do Not Sell My Information

      Property of TechnologyAdvice.
      © 2021 TechnologyAdvice. All Rights Reserved

      Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.

      ×