Proxmox Cluster and Veeam

[Springtime]

Hello,
can someone possibly point me in the right direction? I am trying to understand how to best setup Veeam to backup our new Proxmox servers (3 in a cluster).
Usually with Azure HCI Cluster, we would point Veeam to the cluster, and no matter where the VM is, it will get backed up.
However, Proxmox is working with workers. So each server has to have a worker, so my understanding.
Then I'd have a job to backup up... but that one only sees single nodes or VMs on those nodes.
Now, since this is not a datacenter, I'm ok with Veeam backing up only what is on the appropriate node (for us, everyhting is always on node 1, node 2 is only a HA node, and node 3 is basically also HA, but mainly there as a witness).
So when VMs move to other nodes, they will be not backed up...

However, I am wondering, if this is the right approach? Is there a better one?

Thanks

 

[bbgeek17]

Hi @Springtime,

Have you tried running a backup job for a VM that moved across nodes and it failed, or are you theorizing on what might happen?
Keep in mind that Veeam PVE integration is entirely developed and supported by Veeam (www.veeam.com). So reaching out to Veeam might be your quickest option.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[ceelight]

You have to add each node to Veeam and you have to install a worker for each node. So 3 nodes, three workers.

 

[Springtime]

Have you tried running a backup job for a VM that moved across nodes and it failed, or are you theorizing on what might happen?

At the point of the post, no. But the theory has proven right - Backup failed indeed.

You have to add each node to Veeam and you have to install a worker for each node. So 3 nodes, three workers.

That I did. Actually only two, because 3rd node is only a simple laptop which is playing quorum.

 

[bozkalkan]

If you are running a large infrastructure and your VMs are distributed across nodes with HA (High Availability), assigning the VMs under a pool and selecting the pool tag in your Veeam policy instead of selecting individual VMs would be a healthier solution.

 

[barberos]

I am also connecting veeam to proxmox but i am unable because my management is under a vlan on the vmbr, but you cannot choose a vlan when adding a worker only sdn....

 

[ceelight]

Yes, you can add a VLAN to the workers NIC. We also do this. Let Veeam install the worker. When it's finished and starting up just edit the NIC and enter the VLAN ID. It will immediately connect to the VLAN.

 

[barberos]

Yes, you can add a VLAN to the workers NIC. We also do this. Let Veeam install the worker. When it's finished and starting up just edit the NIC and enter the VLAN ID. It will immediately connect to the VLAN.

Thank you for the reply, i was going to try this today.
Good to hear that this works.
The answer of bozkalkan is the way to go i think.