Disaster recovery (DR) is one of most important use cases that we hear from our customers. Having your own DR site in the cloud ready and on standby, without having to pay for the hardware, power, bandwidth, cooling, space and system administration and quickly launch resources in cloud, when you really need it (when disaster strikes in your datacenter) makes the AWS cloud the perfect solution for DR. You can quickly recover from a disaster and ensure business continuity of your applications while keeping your costs down.
Disaster recovery is about preparing for and recovering from a disaster. Any event that has a negative impact on your business continuity or finances could be termed a disaster. This could be hardware or software failure, a network outage, a power outage, physical damage to a building like fire or flooding, human error, or some other significant disaster.
Business continuity depends on the efficient, uninterrupted flow of data across an organization. Even a brief lapse in workload continuity can mean thousands of lost sales opportunities, disruption to production, and compromised customer trust.
Businesses of all sizes are using AWS to enable faster disaster recovery of their critical IT systems without incurring the infrastructure expense of a second physical site. AWS supports many disaster recovery architectures, from those built for smaller workloads to enterprise solutions that enable rapid failover at scale.
Depending on your Recovery Time Objective (RTO) and Recovery Point Objective (RPO) – two commonly used industry terms when building your DR strategy – you have the flexibility to choose the right approach that fits your budget. Recover Point Objective (RPO) is the maximum targeted period in which data might be lost from an IT service due to a major incident. Recovery Time Objective (RTO) is a targeted time period after which a business process must be restored after a disaster or disruption to service.
The approaches could be as minimum as backup and restore from the cloud or full-scale multi-site solution deployed in onsite and AWS with data replication and mirroring.
AWS Disaster Recovery
AWS Offer four levels of DR support across a spectrum of complexity and time.
- Backup & Restore
- Pilot Light
- Warm standby
- Hot standby
It is clear from above the diagram Backup and Restore is the cheapest option and Hot standby is most costly option. It is totally depending upon our use case which one is more important for our business either time or money. According we opt the best strategy.
Backup & Restore
Suitable for services that can sustain long recovery time ad has low priority. We can store our data on Amazon S3 storage, making them immediately available if a disaster occurs. If we have a large amount of data that needs to be stored on Amazon S3, ideally, we would use AWS Export/Import or even AWS Snowball to store our data on S3 as soon as possible.
AWS Storage Gateway enables snapshots of your on-premise data volumes to be transparently copied into Amazon S3 for backup.
The term “Pilot Light” is often used to describe a DR scenario where a minimal version of an environment is always running in the cloud. With AWS you can maintain a Pilot Light by configuring and running the most critical core elements of your system in AWS like Database. When the time comes for recovery, you can rapidly provision a full-scale production environment around the critical core. It is suitable for low RTO and RPO requirements. Third party option like CloudEndure and Racemi.
A Warm Standby scenario is an expansion of the Pilot Light scenario where some services are always up and running. Once a disaster occurs, infrastructure located on AWS takes over the traffic and performs its scaling and converting to a fully functional production environment with minimal RPO and RTO.
This is a suitable solution for core business-critical functions and in cases where RTO and RPO need to be measured in minutes.
Hot standby (multi-site)
The Multi-Site is a solution for an infrastructure that is up and running completely on AWS as well as on an “on-premise” data center. By using the weighted route policy on Amazon Route 53 DNS, part of the traffic is redirected to the AWS infrastructure, while the other part is redirected to the on-premise infrastructure. Suitable for requirement where RTO and RPO is near zero. It is a highest cost option of DR.
Third Party solution
Third party solution are also available in AWS market place like.