Cloud replication and backup.Immutable copies that cross environments.
Cloud replication and backup moves copies of your data between your cluster and a public cloud, in either direction. Backup copies are immutable, and recovery steps are written down with your team.
Replication and backup across clouds.Your cluster to the cloud, or the cloud to your cluster.
Inside a cluster, Ceph already keeps three copies of every block on different nodes. That protects you from a failed disk or node. It does not protect you from losing the environment itself, or from someone deleting data on purpose.
Cloud replication and backup puts a copy somewhere else. Keep production on your cluster and send copies to AWS, Azure or Google Cloud. Or run production in the cloud and keep copies on single-tenant hardware you can name.
- Cluster to public cloud
- Public cloud to cluster
- Immutable copies that cannot be changed or deleted once written
- Private connections available for the transfer path
What the service covers.Defined with your team during design.
- Direction
- Either way: from your cluster to a public cloud, or from a public cloud to your cluster.
- Clouds
- AWS, Azure and Google Cloud.
- Copy type
- Replication for fast recovery, backups for point-in-time history, or both.
- Immutability
- Backup copies cannot be changed or deleted once written.
- Recovery plan
- Recovery steps documented with your team, so everyone knows who does what.
- Support
- 24/7/365 U.S. engineers by ticket and phone.
What it protects against.Different failures, different copies.
Ransomware
Immutable copies stay intact even if production data is encrypted or deleted.
Losing an environment
A copy in another environment is still there if one site or one cloud account is unavailable.
Retention needs
Keep long-term history in the environment that fits your retention and audit requirements.
A recovery plan people can follow.Copies are only half the job.
A copy you cannot restore from is not much help. So along with replication and backup, we write down the recovery steps with your team: what comes back first, where it runs, who makes the call and how traffic gets switched.
When your environment changes, such as a new application or a workload moving between your cluster and the cloud, we update the plan so it matches what you actually run.
Questions, answered.
How is this different from Ceph's three copies?
Ceph protects against disk and node failures inside the cluster. Replication and backup to a public cloud gives you a copy outside the cluster entirely.
Can the cloud be the primary and the cluster the backup?
Yes. Replication and backup run in either direction.
Who writes the recovery steps?
We document them with your team, so the plan reflects how your applications actually come back.
Does replication traffic go over the internet?
It can use a private connection to AWS, Azure or Google Cloud instead, where one is available for your provider and metro.
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.