What is cloud disaster recovery?
Cloud disaster recovery explained: RTO and RPO, the four strategies from backup and restore to multi-site active/active, how to choose, and why testing matters.
Short answer
Cloud disaster recovery is the set of plans and systems that restore your applications and data in another location after an outage. It is defined by two targets: recovery time objective (RTO), how long you can be down, and recovery point objective (RPO), how much data you can lose. Tighter targets need more infrastructure kept ready, which costs more.
By the Celestibia Solutions engineering team · Published
RTO and RPO
Both are business decisions before they are technical ones. Set them per application: a payment system and an internal reporting tool rarely need the same targets.
Recovery time objective (RTO)
The longest acceptable time between the outage and the service being usable again. An RTO of four hours means the business has agreed it can operate without the system for up to four hours.
Recovery point objective (RPO)
The largest acceptable amount of data loss, measured in time. An RPO of fifteen minutes means losing at most the last fifteen minutes of changes, which requires replication at least that frequent.
The four strategies
Backup and restore
Data is backed up to another region and infrastructure is rebuilt from code when needed. Lowest cost, slowest recovery: typically hours.
Pilot light
Data is replicated continuously and core components such as databases stay running in the recovery region, with application servers switched off until needed.
Warm standby
A scaled-down but fully working copy of the environment runs in the recovery region and is scaled up on failover. Recovery in minutes.
Multi-site active/active
The workload serves traffic from more than one region at all times. Near-zero recovery time, highest cost and the most complex to run.
How to choose
- Start from the RTO and RPO the business has agreed, not from a preferred architecture.
- Estimate what an hour of downtime costs, and compare it with the yearly cost of each strategy.
- Check regulatory requirements for data location and recovery, which may narrow the options.
- Use different strategies for different applications; one size rarely fits a whole estate.
Disaster recovery is not high availability
High availability keeps a system running through the failure of a server or an Availability Zone. Disaster recovery brings it back after something larger: the loss of a region, corrupted data, a ransomware attack or a bad deployment that damages data. A workload spread across three Availability Zones is highly available and can still have no disaster recovery.
Why testing decides whether it works
An untested recovery plan is a guess. Backups that have never been restored may be incomplete, runbooks drift from the real environment, and people forget steps they perform once a year. Run failover exercises on a schedule, measure the recovery time and data loss actually achieved, and compare them with the targets.
Key takeaways
- RTO is how long you can be down; RPO is how much data you can lose.
- The four strategies trade cost against recovery speed.
- High availability does not replace disaster recovery.
- A plan that has not been tested should not be counted on.
Related questions
What is the difference between backup and disaster recovery?
Backup is a copy of your data. Disaster recovery is the whole capability to restore service: the data, the infrastructure it runs on, the network, the runbooks and the people. Backup is one part of it.
Which AWS services are used for disaster recovery?
Common ones are AWS Backup for scheduled, cross-region backups, AWS Elastic Disaster Recovery for continuous replication of servers, cross-region replication in Amazon S3 and the database services, and Amazon Route 53 for failover routing.
Does Celestibia design and test disaster recovery?
Yes. Celestibia designs RTO and RPO targets, builds backup, pilot-light and warm-standby architectures, and runs tested failover on AWS, Azure and Google Cloud.
How Celestibia helps
Related guides
Further reading
Want this applied to your environment?
A Celestibia engineer can review your setup and turn this guidance into a concrete plan. The first assessment is free.
What happens next
- Answer six questions about your cloud setup, spend and priorities. It takes about three minutes.
- A Celestibia engineer reviews your answers within one business day.
- You get tailored recommendations and the AWS programs you are likely to qualify for.
- sales@celestibia.com
- Phone
- +91 8308535810
Monday to Friday, 10 AM to 7 PM IST
