[SOLVED] DR configuration in Proxmox

AndyKosh

New Member
Nov 10, 2025
20
2
3
I've setup 3 node proxmox test cluster (version9). I'm using share LVM with FC storage (netapp) & backup using Veeam. Need to know, how to setup disater reovery for my test VMs? is there any tool/application which provides a similar feature like SRM in broadcom?
 
Hi!
There is no "SRM", at least provided by Proxmox. But you get internal backups, or you can use PBS. But all that is more about replacing the Veeam part, than the SRM. However, by using PBS, and adding a layer of backup for the hosts themselves, you can easily have a setup that provides DR that way, using a PBS remote for example, and automating restore in case of a site destruction..

I do not know of a third party open source solution for that, and Proxmox has PBS, which is awesome, but will require a bit of planning and automating to make it actually useful for that scenario!
Cheers,
Gilou
 
I've setup 3 node proxmox test cluster (version9). I'm using share LVM with FC storage (netapp) & backup using Veeam. Need to know, how to setup disater reovery for my test VMs? is there any tool/application which provides a similar feature like SRM in broadcom?
Veeam recovery, to my understanding, can be performed “online,” meaning the VMs become available as soon as the recovery process is initiated. Proxmox Backup Server (PBS) definitely supports this capability.

That said, if IP addressing changes during recovery, you will need to design a custom recovery procedure that accommodates those changes.

My understanding is that Proxmox Data Management (PDM) is intended to address this business requirement over time, but it does not cover this use case yet.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
Coming back to this in case it helps you or others searching for an SRM equivalent on Proxmox.

With shared LVM on NetApp FC and Veeam already in place, the realistic options are:

1. Veeam restore to the DR cluster. Veeam supports Proxmox VE, so you can restore (or instantly recover) VMs on a second cluster. RPO is your backup interval and RTO depends on restore speed and data size.

2. NetApp SnapMirror at the array level. Fast and storage native, but Proxmox will not orchestrate it: you present the LUNs on the DR cluster, rescan, recreate the VM configs, change IPs and power on in order, all scripted yourself. That scripting is where most of the risk sits.

3. PBS with a remote sync to the DR site, then restore. Supported and simple, with the same RPO and RTO trade off as option 1.

4. A dedicated DR tool. Disclosure: I work on KVMDR, which does near sync replication between independent Proxmox clusters with SRM style orchestrated failover, failback, Re-IP and non disruptive DR tests. Happy to share details if useful.

For a test environment, option 1 or 3 is a good start. Whatever you pick, run a full failover test, including IP changes, before you rely on it.