Veeam Backup Issue with Offline VM on LVM ontop SAN

T

totae

Member
May 27, 2023
26
1
8
Hello,

I am experiencing an issue when backing up an offline VM on SAN storage using LVM with Veeam.

If the VM is online, the backup works normally. However, when the VM is powered off, the backup fails.

There are two types of issues observed:
  1. The backup task remains at 0% for a long time.
taskrunning.png

On the Proxmox side, the task also remains at 0%, and the syslog only shows the following message:

On Proxmox Task still running 0% just show this on syslog.
Code: 
May 08 18:16:12 vm02 pvestatd[2642]: unable to get memory stat for 102 - can't open '/sys/fs/cgroup/qemu.slice/102.scope//memory.current' - No such file or directory
May 08 18:16:12 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2600.
May 08 18:16:12 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2601.
May 08 18:16:12 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2602.
May 08 18:16:12 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2603.
May 08 18:16:12 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2604.
May 08 18:16:12 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2605.
May 08 18:16:22 vm02 pvestatd[2642]: unable to get memory stat for 102 - can't open '/sys/fs/cgroup/qemu.slice/102.scope//memory.current' - No such file or directory
May 08 18:16:22 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2600.
May 08 18:16:22 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2601.
May 08 18:16:22 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2602.
May 08 18:16:22 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2603.
May 08 18:16:22 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2604.
May 08 18:16:22 vm02 pvestatd[2642]: Use of uninitialized value in multiplication (*) at /usr/share/perl5/PVE/QemuServer.pm line 2605.


2. Another error message displayed in Veeam is :
nbderror.png


Could anyone please help suggest how to resolve this issue?

Best Regards,

Veeam Version 12.3.2.4165 + Proxmox Plugin 12.1.5.17

pveversion
Code: 
# pveversion --verbose
proxmox-ve: 9.1.0 (running kernel: 7.0.0-3-pve)
pve-manager: 9.1.9 (running version: 9.1.9/ee7bad0a3d1546c9)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-7.0: 7.0.0-3
proxmox-kernel-7.0.0-3-pve-signed: 7.0.0-3
proxmox-kernel-6.17: 6.17.13-6
proxmox-kernel-6.17.13-6-pve-signed: 6.17.13-6
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
ceph-fuse: 19.2.3-pve2
corosync: 3.1.10-pve2
criu: 4.1.1-1
frr-pythontools: 10.4.1-1+pve1
ifupdown2: 3.3.0-1+pmx12
intel-microcode: 3.20251111.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.1
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.7
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.2
libpve-cluster-perl: 9.1.2
libpve-common-perl: 9.1.11
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.3.0
libpve-notify-perl: 9.1.2
libpve-rs-perl: 0.13.0
libpve-storage-perl: 9.1.2
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-4
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-4
proxmox-backup-client: 4.2.0-1
proxmox-backup-file-restore: 4.2.0-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.9
pve-cluster: 9.1.2
pve-container: 6.1.5
pve-docs: 9.1.2
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-3
pve-ha-manager: 5.2.0
pve-i18n: 3.7.1
pve-qemu-kvm: 10.1.2-7
pve-xtermjs: 5.5.0-3
qemu-server: 9.1.9
smartmontools: 7.4-pve1
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2
zfsutils-linux: 2.4.1-pve1
 
Hello bbgeek17,
bbgeek17 said:
You should also reach out to Veeam or post in their forum. They have a special way of integrating with PVE and the PVE devs have no control and don't test this combination.

Cheers

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Thank you for the suggestion. If anyone has encountered this issue and found a solution, please let me know.

I'm going to open a support case with Veeam regarding this issue. Thank you.

Best Regards,
 
You must log in or register to reply here.
Top Bottom
Back