With disaster recovery playing such an important role in the security of your cloud, it’s vital to be aware of some of the areas where your organization might be unknowingly at risk. Three of the most common and critical mistakes made involve mixing up disaster recovery, high availability and fault tolerance, thinking that your infrastructure is immune to failure and confusing disaster recovery with continuity of operations planning.
Mixing Up Disaster Recovery, High Availability and Fault Tolerance
Although disaster recovery, high availability and fault tolerance may seem like they refer to the same concept and solve the same issues, this isn’t actually the case. High availability, for example, is designed to address service interruptions whereas disaster recovery aims to address major disasters. This means that regardless of having a core router with high availability and even fault tolerance, your network is still vulnerable to a disaster.
Under those circumstances, while your application remains unaffected in the cloud, the connection that your organization has to it has been severed and requires the restoration of IT system access that is normally provided for by your disaster recovery plan.
Thinking That Your Infrastructure is Immune to Failure
It’s to be expected that most organizations focus on designing a system that doesn’t fail, however, they sometimes then infer that a disaster recovery plan is no longer needed. Unfortunately, an all too well-known fact is that ignoring something doesn’t make it go away, it simply leaves us unprepared.
In order to be adequately prepared, the possibility of failures can’t be denied. Instead, they need to be planned for and mitigated throughout each phase of the design process – automatically or manually depending on where automation is possible.
Confusing Disaster Recovery With Continuity of Operations Planning
Another critical mistake made by organizations is assuming that disaster recovery and continuity of operations planning are interchangeable. As with DR, HA and FT discussed in our first point, each planning aspect has it’s own specific purpose that it serves.
While disaster recovery is heavily IT-focused, continuity of operations planning encompasses many facets such as processes, people and all other business essentials. These two plans also differ in terms of when they are brought into effect. A disaster recovery plan is implemented prior to a major event, and a continuity of operations plan dictates how to operate during a major event.
Disaster recovery planning will continue to play an important role in cloud computing and should not be regarded as an interchangeable aspect of securing your infrastructure. Companies desiring to safeguard against failure should include DR along with HA, FT and COOP.