On June 9th our AWS Cloud Solutions Architect Laith Al-Saadoon was featured in TechTarget’s SearchAWS article discussing AWS redundancy and Disaster Recovery (DR) set up. An excerpt of the article can be found below.
AWS Redundancy, DR Set Up No Piece of Cake
by Alan R. Earls | TechTarget
It is now affordable – and recommended – for IT operations of all shapes and sizes to back up data and workloads in the cloud, but recreating a data center requires a careful approach.
Before the cloud era, only a few organizations – generally the biggest and best-funded – could afford to have a second data center for business continuity or disaster recovery. The costs of hardware, space and personnel were too prohibitive for others.
With the cloud, however, adding capacity is relatively easy and dramatically less expensive. With multiple cloud locations and AWS availability zones, enterprises have the ability to build applications that can be more scalable and available than tradition on-premises apps. However, turning AWS redundancy into a fully functioning secondary off-site data center is not necessarily easy.
The use of cloud services for DR has multiple facets. Business risks, such as single points of failure, systems outages or even full data center outages, can be mitigated through cloud-based DR. Traditional on-premises disaster recovery requires significant investment in storage, server and network architecture to replicate production infrastructure, or an acceptable subset of production.
As businesses create applications in a paradigm in which underlying infrastructure is less important, entire sections of applications, availability regions in the cloud or on-premises data centers can be added or removed to the resource pool and used dynamically.
Netflix uses this methodology for testing AWS redundancy with its Simian Army. Entire sections of the Netflix infrastructure may be randomly and arbitrarily deleted, but AWS redundancy and DR are built into the software, which is expected to recover autonomously.
But don’t underestimate the challenges of setting up duplicate infrastructure in the cloud.
Those factors include the need to replicate the system from a given hypervisor or a physical server to a cloud-based image. Although there are tools that can help, it remains a tricky proposition.
The other big issue is continuous replication to the DR environment. “How do you control that so it is low overhead and not impacting production or saturating your network – or sacrificing performance?” Al-Saadoon asked.
There also are technical issues like encryption and compression, and especially deduplication. “You should make sure you are not sending a bit of data you have already sent before,” he said.
Data Center Duplication Marches On
Fortunately, the process of setting up and duplicating data centers, or at least big parts of data centers, is evolving quickly.
“Once you have a production environment in AWS, it is far simpler to create a multi-region disaster recovery or business continuity system, because you have services like S3 [Simple Storage Service] for cross-region replication and EBS [Elastic Block Store] and RDS [Relational Database Service] snapshots that you can send from on region to another,” Al-Saadoon said. With AWS, the barriers to duplicating to and within the cloud are lower. However, while it may seem deceptively simple, it is not as simple as pushing a button. Enterprises seek DR or business continuity efforts that can bring a business back into operation in less than 10 minutes, but it’s hard to achieve.
Enterprises looking for business and disaster recovery through AWS should evaluate its capabilities. For example, an IT team can replicate RDS and EBS snapshots and Amazon Machine Images. Those capabilities may or may not meet an enterprise’s recovery time objective and recovery point objectives.
AWS also provides multiple availability zones for production workloads, which may be enough for many organizations looking for AWS redundancy.
To read the full article, please visit TechTarget.