We have Proxmox Cluster with a few CT's and a lot of VM's. Every night all CT's and VM's are backupped to a Proxmox Backup Server.
I noticed an error for some CT's with the following error:
110: 2024-04-11 00:00:42 INFO: Starting Backup of VM 110 (lxc)
110: 2024-04-11 00:00:42 INFO: status = running
110: 2024-04-11 00:00:42 INFO: CT Name: LXCDCNC01
110: 2024-04-11 00:00:42 INFO: including mount point rootfs ('/') in backup
110: 2024-04-11 00:00:42 INFO: found old vzdump snapshot (force removal)
110: 2024-04-11 00:00:43 INFO: backup mode: snapshot
110: 2024-04-11 00:00:43 INFO: ionice priority: 7
110: 2024-04-11 00:00:43 INFO: create storage snapshot 'vzdump'
110: 2024-04-11 00:00:44 ERROR: Backup of VM 110 failed - command 'mount -o ro,noload /dev/rbd-pve/a81f4ddc-612f-41b2-a976-a8654eeb32ee/Productie-Diensten/vm-110-disk-0@vzdump /mnt/vzsnap0//' failed: exit code 32
Shutting down the CT and booting it fixes the backup error and creates a valid backup of the CT.
What I notice is that this happens when the CT's are being migrated to another host when updating and rebooting a host bc of a new kernel. CT is being shutdown on host and started on a different host but apparently the Proxmox Backup Server doesn't get it when it wants to perform a backup during the night?
I noticed an error for some CT's with the following error:
110: 2024-04-11 00:00:42 INFO: Starting Backup of VM 110 (lxc)
110: 2024-04-11 00:00:42 INFO: status = running
110: 2024-04-11 00:00:42 INFO: CT Name: LXCDCNC01
110: 2024-04-11 00:00:42 INFO: including mount point rootfs ('/') in backup
110: 2024-04-11 00:00:42 INFO: found old vzdump snapshot (force removal)
110: 2024-04-11 00:00:43 INFO: backup mode: snapshot
110: 2024-04-11 00:00:43 INFO: ionice priority: 7
110: 2024-04-11 00:00:43 INFO: create storage snapshot 'vzdump'
110: 2024-04-11 00:00:44 ERROR: Backup of VM 110 failed - command 'mount -o ro,noload /dev/rbd-pve/a81f4ddc-612f-41b2-a976-a8654eeb32ee/Productie-Diensten/vm-110-disk-0@vzdump /mnt/vzsnap0//' failed: exit code 32
Shutting down the CT and booting it fixes the backup error and creates a valid backup of the CT.
What I notice is that this happens when the CT's are being migrated to another host when updating and rebooting a host bc of a new kernel. CT is being shutdown on host and started on a different host but apparently the Proxmox Backup Server doesn't get it when it wants to perform a backup during the night?