Proxmox Veeam B&R recognize moved VM within a cluster?

[liwicom]

Hi all,

We are currently testing Proxmox 12.2 on a test cluster with three nodes. We've encountered an issue where, if we move a VM within the same cluster from one node to another, the backup fails because the configuration file cannot be found.

Our setup uses ZFS, and we replicate VMs for failover and load distribution.

Is there any plan for the Proxmox V2 plugin to allow Veeam to recognize a moved VM within a cluster when not using shared storage, similar to how it works when backing up a VM with VMware and vCenter Server?

Thanks for your efforts,


Andreas

[liwicom]

Hi everybody,

In my test, the time between backups was too short when I moved the VM. However, after rescanning the Proxmox nodes in the backup infrastructure, Veeam Backup & Replication updates the VM's location, and the backup completes successfully.

I believe this location update happens periodically, so everything is fine—Veeam does track where the VM is located; it just needs a bit of time to do so.

Thanks, everyone, for your efforts!


Andreas

[nefes]

For future reference, automatic infrastructure rescan happens every 15 minutes.

[danswartz]

I have a 2-node cluster. VM named 'Certbot' on hyper3. Migrated to hyper6. Created a backup job containing only that guest. Ran the job ok. Migrated back to hyper3. Tried to run job again. Failed as follows:

2/12/2026 11:51:28 AM :: Certbot : Configuration file 'nodes/hyper6/qemu-server/100.conf' does not exist

If it makes a difference, disks were on local-zfs storage, so migration was slow (as expected). I've noticed when I add VMs to a job, it requires me to pick them from the host - they are not visible at cluster level (which I vaguely remember from vsphere and hyper-v). Is this expected? If so, this seems like a major deficiency, no? If someone can't migrated guests to different nodes without editing jobs, ouch!

[rovshan.pashayev]

Hello Dan,

I’ve moved your question to the existing topic.
Please try rescanning the Proxmox VE hosts in the Veeam Backup & Replication infrastructure.

[danswartz]

Ah, ok. I’ll keep an eye out.

[danswartz]

Still no joy. Migrated a couple of guests 2 hours ago, and they still show grayed out . I even rescanned all three nodes to no effect.

[rovshan.pashayev]

Hi Dan,

I’ll need to ask you to submit a Support Case and share the case number here for reference.

[danswartz]

Community Edition. Don't think it's corruption since after reporting this, I created a VM of B&R to replace the physical one and reconfigured from scratch.

[rovshan.pashayev]

Hello Dan,

You still can submit the Support Case:
Community edition gets support on best effort. Best effort means, only if there is free capacity in our customer support team, cases from users of our free products will be worked on.
Please see our support policy for more information: https://www.veeam.com/support-policy.html

[danswartz]

thanks!

[danswartz]

Interesting data point. Confirmed that all 3 backup jobs were ok (no grayed out guests.). Went to proxmox console and migrated 2 guests. Went and read a book for awhile. Just sat down now and checked all 3 jobs, and they all show those 2 guest grayed out. NB: I did not run anything, and the 2 migrations were at 15:47 and 15:50. I checked the 3 jobs at 16:40 so almost 1 hour. Before I open a case, which logs do you need? No jobs were run, so I assume whatever would have infrastructure updates?

[danswartz]

This is crazy. At this point, I can't reliably do backups. I edit job X. 3 specific guests show grayed out. I remove and re-add them, and re-edit job X. Now 2 other guests are grayed out. Yes I've done a rescan on all 3 hosts, even did a refresh in the add guests dialog. Only 'fix' seems to be rebooting the Veeam VM. I suppose this is a work-around, but Good Lord!