Proxmox disaster recovery: the complete guide
Everything you need to plan and run disaster recovery on Proxmox VE — what Proxmox gives you, where the gaps are, and how to achieve tested, orchestrated recovery across sites.
Disaster recovery vs backup
Backup and DR are not the same thing. Backup protects against data loss over time — long retention, point-in-time restores (this is what Proxmox Backup Server does well). Disaster recovery is about getting workloads running again at another site quickly after a failure: low RPO, fast RTO, and a tested failover process. You need both.
What Proxmox VE gives you natively
- ZFS replication (
pvesr) — asynchronous, down to ~1-minute intervals, ZFS-only. - Ceph RBD mirroring — snapshot or journal-based replication between Ceph clusters.
- Proxmox Backup Server — efficient incremental backups with deduplication.
What's missing is the orchestration: recovery plans, non-disruptive DR testing, one-click failover and failback, and network re-mapping — plus replication for storage other than ZFS and Ceph.
RPO and RTO, briefly
RPO (Recovery Point Objective) is how much data you can afford to lose — set by your replication interval. RTO (Recovery Time Objective) is how long recovery may take — set by how automated and tested your failover is. Good DR drives both down: frequent replication for RPO, orchestrated recovery plans for RTO.
Non-disruptive DR testing
A DR plan you've never tested is a guess. The gold standard is non-disruptive test failover: boot your replicated VMs in an isolated network, verify they come up and applications work, then tear it down — all without touching production or pausing replication. This is exactly what tools like VMware SRM and Zerto provide, and what ProxDR brings to Proxmox.
Failover and failback
Planned failover gracefully moves workloads to the recovery site (final sync, quiesce, power on). Unplanned failover recovers from the last replicated point when the primary is gone. Failback reverses replication and returns workloads once the primary is healthy — the step most DIY setups get wrong.
Getting SRM/Zerto-class DR on Proxmox
ProxDR is purpose-built for this. It installs on a Linux VM, connects to your Proxmox clusters, and adds near-continuous replication (on any storage), non-disruptive DR testing, recovery plans, and one-click failover/failback — managed from one web UI at every site, with no single point of failure. See how it compares to VMware SRM and Zerto.
Frequently asked questions
Does Proxmox have built-in disaster recovery?
Proxmox VE offers storage-level replication (ZFS via pvesr, Ceph via RBD mirroring) and backups via Proxmox Backup Server, but no DR orchestration — no recovery plans, non-disruptive testing, or one-click failover. ProxDR adds that layer.
What is a good RPO for Proxmox VMs?
On ZFS/Ceph, ProxDR can orchestrate replication down to about 1 minute. On other storage its dirty-bitmap engine targets 10 minutes to 1 hour. The right RPO depends on how much data you can afford to lose per workload.
Can I do disaster recovery on LVM-thin storage in Proxmox?
Not natively — Proxmox only replicates ZFS and Ceph. ProxDR's storage-agnostic engine, built on QEMU dirty bitmaps, replicates VMs on LVM-thin and other backends too.