Disaster Recovery Across Cloud and Data Centre
Building a second data centre for disaster recovery used to be out of reach for most organisations. Using the cloud as a recovery site — or a second cloud region — changes the economics. The design work, however, still matters.
Start with RTO and RPO
- Recovery Time Objective: how long each system can be down.
- Recovery Point Objective: how much data you can afford to lose.
These numbers drive every other decision and cost.
Common patterns
- Backup and restore: cheapest, slowest — hours to days.
- Pilot light: data replicated continuously, minimal servers running, scale up on failover.
- Warm standby: a scaled-down copy always running.
- Active-active: both sites serve traffic; most expensive, fastest.
Do not forget the network
- How do users and branches reach the DR site?
- Do DNS records, public IPs and VPNs fail over?
- Is there enough bandwidth for replication and for users after failover?
Test, then test again
Run a planned failover at least once a year, measure the real RTO and fix what broke.
We design DR networks and private cloud connectivity. Learn about Multi Cloud Connect or discuss your DR plan.
