Analytical use of cookies
Disaster Recovery
Disaster Recovery for VMware, Hyper-V and Proxmox
DR is not only backup. DR asks how the company starts after an incident: where VMs run, how network, DNS, firewall, login, data and service priorities work, and who decides about failover.
Short answer
DR is not only backup. DR asks how the company starts after an incident: where VMs run, how network, DNS, firewall, login, data and service priorities work, and who decides about failover.
RPO/RTO without magic
Each service needs accepted data loss and downtime. ERP, mail, files and monitoring have different requirements.
VMware, Hyper-V, Proxmox
Each platform has different snapshots, replicas, backup and restore mechanisms. DR must include hypervisor, storage and network.
Network after an incident
After VM restore you need addressing, DNS, firewall, VPN, administrator access, certificates and user-communication procedure.
Runbook and test
A DR plan must be tested. The runbook describes service start order, decision makers, failover conditions and failback steps.
Practical checklist
- List services and prioritise: ERP, AD/LDAP, DNS, mail, databases, files, applications and monitoring.
- For each service define RPO, RTO, dependencies, data size and minimal startup resources.
- Choose method: backup, replication, standby VM, private cloud or colocated customer hardware.
- Prepare runbook: startup order, network, DNS, firewall, access, communication and decision criteria.
- Test DR at least partially and record real recovery time.
Frequently asked questions
Is backup enough for DR?
Not always. If services must start quickly, you need an alternate environment, network design and startup-order plan.
Can Proxmox be included in DR?
Yes, but backup/replication tools, storage, network and test procedure must fit the installation.
Can DR run in DataHouse?
Yes. Use a backup repository, private cloud, dedicated servers, colocation or a private colocation room.