Disaster recovery

This article is about business continuity planning. For societal disaster recovery, see emergency management.
For other uses, see DR (disambiguation).

Disaster recovery (DR) involves a set of policies and procedures to enable the recovery or continuation of vital technology infrastructure and systems following a natural or human-induced disaster.[1] Disaster recovery focuses on the IT or technology systems supporting critical business functions,[2] as opposed to business continuity, which involves keeping all essential aspects of a business functioning despite significant disruptive events. Disaster recovery is therefore a subset of business continuity.[3]

History

Disaster recovery developed in the mid- to late 1970s as computer center managers began to recognize the dependence of their organizations on their computer systems. At that time, most systems were batch-oriented mainframes which in many cases could be down for a number of days before significant damage would be done to the organization.[4]

As awareness of the potential business disruption that would follow an IT-related disaster, the disaster recovery industry developed to provide backup computer centers, with Sun Information Systems (which later became Sungard Availability Services) becoming the first major US commercial hot site vendor, established in 1978 in Philadelphia.[5]

During the 1980s and 90s, customer awareness and industry both grew rapidly, driven by the advent of open systems and real-time processing which increased the dependence of organizations on their IT systems. Regulations mandating business continuity and disaster recovery plans for organizations in various sectors of the economy, imposed by the authorities and by business partners, increased the demand and led to the availability of commercial disaster recovery services, including mobile data centers delivered to a suitable recovery location by truck.

With the rapid growth of the Internet through the late 1990s and into the 2000s, organizations of all sizes became further dependent on the continuous availability of their IT systems, with some organizations setting objectives of 2, 3, 4 or 5 nines (99.999%) availability of critical systems. This increasing dependence on IT systems, as well as increased awareness from large-scale disasters such as tsunami, earthquake, flood, and volcanic eruption, spawned disaster recovery-related products and services, ranging from high-availability solutions to hot-site facilities. Improved networking meant critical IT services could be served remotely, hence on-site recovery became less important.

The rise of cloud computing since 2010 continues that trend: nowadays, it matters even less where computing services are physically served, just so long as the network itself is sufficiently reliable (a separate issue, and less of a concern since modern networks are highly resilient by design). 'Recovery as a Service' (RaaS) is one of the security features or benefits of cloud computing being promoted by the Cloud Security Alliance.[6]

Classification of disasters

Disasters can be classified into two broad categories. The first is natural disasters such as floods, hurricanes, tornadoes or earthquakes. While preventing a natural disaster is impossible, risk management measures such as avoiding disaster-prone situations and good planning can help. The second category is man made disasters, such as hazardous material spills, infrastructure failure, bio-terrorism, and disastrous IT bugs or failed change implementations. In these instances, surveillance, testing and mitigation planning are invaluable.

Importance of disaster recovery planning

Recent research supports the idea that implementing a more holistic pre-disaster planning approach is more cost-effective in the long run. Every $1 spent on hazard mitigation(such as a disaster recovery plan) saves society $4 in response and recovery costs.[7]

As IT systems have become increasingly critical to the smooth operation of a company, and arguably the economy as a whole, the importance of ensuring the continued operation of those systems, and their rapid recovery, has increased.[8] For example, of companies that had a major loss of business data, 43% never reopen and 29% close within two years.[9] As a result, preparation for continuation or recovery of systems needs to be taken very seriously. This involves a significant investment of time and money with the aim of ensuring minimal losses in the event of a disruptive event.[10]

Control measures

Control measures are steps or mechanisms that can reduce or eliminate various threats for organizations. Different types of measures can be included in disaster recovery plan (DRP).

Disaster recovery planning is a subset of a larger process known as business continuity planning and includes planning for resumption of applications, data, hardware, electronic communications (such as networking) and other IT infrastructure. A business continuity plan (BCP) includes planning for non-IT related aspects such as key personnel, facilities, crisis communication and reputation protection, and should refer to the disaster recovery plan (DRP) for IT related infrastructure recovery / continuity.

IT disaster recovery control measures can be classified into the following three types:

  1. Preventive measures - Controls aimed at preventing an event from occurring.
  2. Detective measures - Controls aimed at detecting or discovering unwanted events.
  3. Corrective measures - Controls aimed at correcting or restoring the system after a disaster or an event.

Good disaster recovery plan measures dictate that these three types of controls be documented and exercised regularly using so-called "DR tests".

Strategies

Prior to selecting a disaster recovery strategy, a disaster recovery planner first refers to their organization's business continuity plan which should indicate the key metrics of recovery point objective (RPO) and recovery time objective (RTO) for various business processes (such as the process to run payroll, generate an order, etc.). The metrics specified for the business processes are then mapped to the underlying IT systems and infrastructure that support those processes.[11]

Incomplete RTOs and RPOs can quickly derail a disaster recovery plan. Every item in the DR plan requires a defined recovery point and time objective, as failure to create them may lead to significant problems that can extend the disaster’s impact.[12] Once the RTO and RPO metrics have been mapped to IT infrastructure, the DR planner can determine the most suitable recovery strategy for each system. The organization ultimately sets the IT budget and therefore the RTO and RPO metrics need to fit with the available budget. While most business unit heads would like zero data loss and zero time loss, the cost associated with that level of protection may make the desired high availability solutions impractical. A cost-benefit analysis often dictates which disaster recovery measures are implemented.

Traditionally, a disaster recovery system involved cutover or switch-over recovery systems. Such measures would allow an organization to preserve its technology and information, by having a remote disaster recovery location that produced backups on a regular basis. However, this strategy proved to be expensive and time-consuming. Therefore more affordable and effective cloud-based systems were introduced.[13]

Some of the most common strategies for data protection include:

In many cases, an organization may elect to use an outsourced disaster recovery provider to provide a stand-by site and systems rather than using their own remote facilities, increasingly via cloud computing.

In addition to preparing for the need to recover systems, organizations also implement precautionary measures with the objective of preventing a disaster in the first place. These may include:

See also

References

  1. ↑ Disaster recovery. Computer Business Research... Retrieved 3 August 2012.
  2. ↑ Systems and Operations Continuity: Disaster Recovery. Georgetown University. University Information Services. Retrieved 3 August 2012.
  3. ↑ Disaster Recovery and Business Continuity, version 2011. IBM. Retrieved 3 August 2012.
  4. ↑ A Brief History of Disaster Recovery, safetynet247.co.uk
  5. ↑ SunGard Data Systems: Company history, fundinguniverse.com
  6. ↑ SecaaS Category 9 // BCDR Implementation Guidance CSA, retrieved 14 July 2014.
  7. ↑ "Post-Disaster Recovery Planning Forum: How-To Guide" (PDF). University of Oregon's Community Service Center. Retrieved 2013-05-23. |first1= missing |last1= in Authors list (help)
  8. ↑ "The 3R’s of Disaster Recovery". Data Recovery Hospital. Retrieved 11 May 2013.
  9. ↑ Business continuity statistics: where myth meets fact. Continuity Central. 24 April 2009. Retrieved 3 August 2012.
  10. ↑ "IT Disaster Recovery Plan". FEMA. 25 October 2012. Retrieved 11 May 2013.
  11. ↑ Gregory, Peter. CISA Certified Information Systems Auditor All-in-One Exam Guide, 2009. ISBN 978-0-07-148755-9. Page 480.
  12. ↑ "Five Mistakes That Can Kill a Disaster Recovery Plan". Dell.com. Retrieved 2012-06-22.
  13. ↑ Alhazmi, Ph. D, Omar (2013). "Evaluating Disaster Recovery Plans Using the Cloud". ResearchGate. Retrieved 2016-04-03.
  14. ↑ Import Storage Domain feature handling Disaster Recovery in oVirt
  15. ↑ Brandon, John (23 June 2011). "How to Use the Cloud as a Disaster Recovery Strategy". Inc. Retrieved 11 May 2013.

Further reading

External links

This article is issued from Wikipedia - version of the Thursday, April 21, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.