Feature
Disaster Recovery
Pick a recovery strategy, plan replication and a standby region, schedule readiness checks, run game-day drills, and fail over and back on AWS.
A recovery plan that has never been run is a guess. OrchesTerra keeps the plan, the standby infrastructure and the evidence that it works in one place.
Choose a strategy
Set your recovery-time and data-loss targets and OrchesTerra helps you pick a strategy: active-active, warm standby, pilot light or backup and restore.
Plan replication and standby
For each workload you choose a standby region and what has to be ready there:
- replication for data stores,
- standby compute and clusters,
- Route 53 failover records that can move traffic to the standby.
The standby is defined in Terraform/OpenTofu like the rest of the estate, so it is reviewed, versioned and covered by drift detection.
Readiness
OrchesTerra checks the pieces a failover depends on and shows them as ready or not: replication healthy, standby cluster up, failover record in place. Schedule the check daily, weekly, every two weeks or monthly, and see a gap before the day you need the standby.
Game-day drills
Run a game-day drill to rehearse the failover. Drills give you evidence for audits and a realistic idea of how long recovery takes.
Failover
When you need it, run the failover you rehearsed, then fail back and re-protect once the primary region is healthy. You can also download a failover pack to keep the runbook outside OrchesTerra.
Related: the Managed DevSecOps team can run DR drills for you.
FAQ
Which clouds are supported?
Disaster recovery covers AWS commercial regions today.
Does this replace our backup tool?
No. It coordinates replication, standby infrastructure and failover. Keep your backup tooling for point-in-time restores.