Cloud Disaster Recovery Planning
Know how long recovery takes and how much data you could lose, then test it. Backup, restore and failover for AWS and Azure, written down as a runbook.
A Backup You Have Never Restored Is a Hope
Many teams have backups switched on and no evidence they work. Others run production and test on one database in one availability zone. Disaster recovery planning starts with two numbers for each system: how quickly it must be back (RTO) and how much data you can afford to lose (RPO). From there we design the cheapest setup that meets them, restore from your backups to prove they work, and write the runbook your team follows on a bad day.
Recovery Options, Cheapest First
Chosen to match your recovery targets, not to maximise spend.
Backup and restore
Automated backups, copied off-account or cross-region, with restores tested on a schedule.
Multi-AZ
Databases and services that survive the loss of one availability zone.
Warm standby
A scaled-down copy in a second region, ready to take traffic.
Safe upgrades
Blue/Green database upgrades with rollback kept until sign-off.
How We Plan Recovery
Targets first, then design, then proof.
Targets
RTO and RPO agreed for each system.
Design
The lowest-cost setup that meets them.
Test
A real restore, timed and checked.
Runbook
Written steps for the day it is needed.
Recovery you have seen work
The output is a tested restore and a runbook, not a diagram of what should happen.
Tested
Restores are run and timed.
Costed
Every option comes with its monthly cost.
Written down
A runbook anyone on the team can follow.
Monitored
Alerts when a backup job fails.
Related case studies
ERP · US · Designed, awaiting go-ahead
Major upgrades for an eight-database ERP fleet
The fleet has a documented path to PostgreSQL 17 with a short switchover, users see a clear maintenance page, and rollback stays available until sign-off.
SaaS · US · In progress
Finding the bottleneck and the savings
The client knows where its performance problem sits, which commitments cut its bill, and why one recommendation adds cost to remove a single point of failure.
Start with a free cloud audit
Read-only access, a written list of findings, and no obligation to continue.
Book a free cloud audit