Backup failed when CRS rebalanced VM during backup queue at specific node

Jan 22, 2022
14
5
23
28
I have backup job of all VMs (3 VMs of 120+ are excluded due to specific reasons) in 9-node PVE 9.2 cluster
1786446330729.png
I have rebalance turned on:
1786446355787.png
Sometimes there is issue that backup starts and also rebalancing thinks that there's a time to rebalance VM. As the backup job does one by one VM backup of the static list, defined at start of backup job at every node - there's issue when the VM is rebalanced during being in queue.
1786446431677.png

Log from backup:
Code:
1063: 2026-08-08 00:20:06 INFO: Finished Backup of VM 1063 (00:00:03)

1116: 2026-08-08 00:20:06 INFO: Starting Backup of VM 1116 (qemu)
1116: 2026-08-08 00:20:06 ERROR: Backup of VM 1116 failed - unable to find configuration file for VM 1116 on node 'beu1'

1132: 2026-08-08 00:20:06 INFO: Starting Backup of VM 1132 (qemu)

My PVE version is:
Code:
# pveversion -v
proxmox-ve: 9.2.0 (running kernel: 7.0.14-8-pve)
pve-manager: 9.2.4 (running version: 9.2.4/5e5ae681198514d4)
proxmox-kernel-helper: 9.2.0
proxmox-kernel-7.0.14-8-pve-signed: 7.0.14-8
proxmox-kernel-7.0: 7.0.14-8
proxmox-kernel-6.17: 6.17.13-21
proxmox-kernel-6.17.13-21-pve-signed: 6.17.13-21
proxmox-kernel-6.17.13-9-pve-signed: 6.17.13-9
proxmox-kernel-6.17.4-2-pve-signed: 6.17.4-2
proxmox-kernel-6.14: 6.14.11-9
proxmox-kernel-6.14.11-9-pve-signed: 6.14.11-9
proxmox-kernel-6.14.11-5-pve-signed: 6.14.11-5
proxmox-kernel-6.14.11-2-pve-signed: 6.14.11-2
amd64-microcode: 3.20251202.1~bpo13+1
ceph: 19.2.3-pve4
ceph-fuse: 19.2.3-pve4
corosync: 3.1.10-pve3
criu: 4.1.1-1
frr-pythontools: 10.6.1-1+pve2
ifupdown2: 3.3.0-1+pmx12
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.2
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.1.1
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.6
libpve-cluster-perl: 9.1.6
libpve-common-perl: 9.1.20
libpve-guest-common-perl: 6.0.5
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.6.7
libpve-notify-perl: 9.1.6
libpve-rs-perl: 0.15.3
libpve-storage-perl: 9.1.7
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 7.0.0-2
lxcfs: 7.0.0-pve1
novnc-pve: 1.7.0-2
proxmox-backup-client: 4.2.3-1
proxmox-backup-file-restore: 4.2.3-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.3
proxmox-kernel-helper: 9.2.0
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.7
proxmox-offline-mirror-helper: 0.7.4
proxmox-widget-toolkit: 5.2.6
pve-cluster: 9.1.6
pve-container: 6.1.12
pve-docs: 9.2.3
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.5
pve-firmware: 3.18-5
pve-ha-manager: 5.2.4
pve-i18n: 3.9.0
pve-qemu-kvm: 11.0.2-1
pve-xtermjs: 6.0.0-2
qemu-server: 9.2.1
smartmontools: 7.5-pve2
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2
zfsutils-linux: 2.4.3-pve1
 
@j.theisen , thank you for your response. TBH, it's not so critical but I wanted to create a thread to mark it as issue. I'd love to see that there's already bugzilla thread with the same issue and somebody thinks the same way :D .

Thank you for the crosslink.
 
  • Like
Reactions: j.theisen