Cross-cloud disaster recovery.Recover somewhere production is not.
Cross-cloud disaster recovery keeps your recovery copy in a different environment from production. If production runs on your cluster, recover in a public cloud; if it runs in the cloud, recover on single-tenant hardware.
The case for cross-cloud disaster recovery.Do not keep the spare in the same house.
A backup that lives in the same environment as production shares its risks. The same account compromise, the same provider issue or the same configuration mistake can reach both.
Cross-cloud disaster recovery separates them. Production runs in one environment, and the recovery copy lives in another one, run under different accounts and different infrastructure. One bad day stays one bad day.
Two common shapes.Pick the direction that matches production.
Cluster first, cloud recovery
Production on your single-tenant cluster. Immutable copies replicate to AWS, Azure or Google Cloud for recovery.
Cloud first, cluster recovery
Production in a public cloud. Recovery copies land on single-tenant hardware in a location you can name.
Cluster to cluster
Need both copies on your own hardware? Replicate to a second metro, such as Chicago and Ashburn.
Learn moreBuilding the recovery plan.Written down before you need it.
- RankWe list your workloads with your team and decide which ones come back first.
- ReplicateWe set up replication and immutable backups to the recovery environment, over private connections where available.
- DocumentRecovery steps are written with your team, so everyone knows who does what.
- RehearseWalk through the plan together and update it when your environment changes.
What a recovery day looks like.Plain steps, a known order.
When production is unavailable, your team and ours follow the written plan. Priority workloads start in the recovery environment from the latest clean copy. Traffic is pointed at the recovery side. Lower-priority systems follow in the agreed order.
Our U.S.-based engineers are on call 24/7/365 by ticket and phone, and they are the same people who built your cluster, so nobody is learning your environment for the first time during an outage.
Questions, answered.
Why not just back up inside the same cloud?
Copies in the same environment share its risks. A separate environment means one account issue or provider issue does not take out both.
Are the recovery copies protected from ransomware?
Backup copies are immutable, so they cannot be changed or deleted once written.
Which clouds can be the recovery side?
AWS, Azure and Google Cloud, or a single-tenant cluster if production runs in the cloud.
Can recovery copies travel over a private connection?
Yes, where a private connection to the provider is available. Options are confirmed per provider and metro during design.
Talk to the engineers who will build it.
Tell us what you run today and where you’re headed. We’ll come back with a design and a fixed monthly price.