Planning a disaster recovery plan for Proxmox with Cloud-PBS
What a Proxmox VE disaster recovery plan should cover: RTO and RPO, why backups alone are not a DRP, and how Cloud-PBS provides off-site, tested recovery.
Most teams running Proxmox VE have backups. Far fewer have a disaster recovery plan. The difference is not a detail: a backup is a file, a DRP is the documented, tested answer to “our infrastructure is down, what now?”. This article is for the person who has to answer that question to management.
Backups are not a recovery plan
A backup tells you the data exists somewhere. A disaster recovery plan tells you, concretely: where you restore, on what hardware, in what order, who does it, and how long it takes. If your backups live on the same site, or worse the same cluster, as the systems they protect, a fire, a flood or a ransomware event takes both at once. That is not a recovery plan. It is a copy.
Two numbers decide everything: RTO and RPO
Before any technical choice, management needs to agree on two targets:
- RPO (Recovery Point Objective): how much data you can afford to lose, measured in time. A 24-hour RPO means a daily backup is enough. A 1-hour RPO does not.
- RTO (Recovery Time Objective): how long the business can run with the system down before the impact becomes serious.
These are business decisions, not IT decisions. They set the cost of the plan. Pretending the RTO is zero for everything is how DRPs become unaffordable and therefore never built.
What a Proxmox DRP must contain
A usable plan answers, in writing:
- Scope. Which VMs are critical, which can wait, which do not matter.
- Off-site copy. Backups in a different physical location, on a system attackers cannot reach from the production network.
- Restore target. The hardware or platform the VMs are restored onto, sized in advance, not improvised during the incident.
- Procedure and ownership. Who declares the disaster, who runs the restore, in what order.
- Proof. A restore test, on a schedule. An untested backup is a hypothesis.
That last point is where most plans fail. Backups succeed quietly for years; the first real restore attempt is during the actual disaster. That is the worst possible moment to discover a gap.
Where Cloud-PBS fits
Cloud-PBS, the LenoIT managed backup service, is built for the off-site copy and the proof. It provides managed Proxmox Backup Server storage in a separate location, isolated from your production network, with client-side encryption so the data is unreadable in transit and at rest. Restore testing is part of the service, not an afterthought, which means your RTO is a measured number rather than a hope.
Paired with Cloud-PVE for the platform and Cloud-PBS for the recovery side, the DRP stops being a document nobody trusts. Talk to us about turning your backups into a recovery plan you can actually stand behind.
Ready to put this into practice?
Cloud-PVE deploys and manages your Proxmox VE infrastructure. Focus on your VMs, not the ops.