backup failed

[ferociousmilkyway]

I am seeing this in the backup log after I have enabled iothread:
111: Jul 29 05:15:03 ERROR: Backup of VM 111 failed - disk 'scsi0' (iothread=on) can't use backup feature currently. Please set backup=no for this drive at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 74.

Is this a feature or a bug?

And if this is a feature then why?

qemu-server: 4.0-85

Using PCI Passthrough on a video card, I've found IO Thread to be a necessary setting to keep DPC latency stable in Windows guests, but I have to disable the flag and reboot prior to every backup.

Any chance this issue will get addressed in PVE 6 with the QEMU bump? I tried the beta, and am still seeing this issue.

Thanks for the great OS!

 

[motox]

PVE 6.0-4 and still the problem exists

 

[spirit]

iothread backup has been implemented some week ago
https://git.proxmox.com/?p=qemu-server.git;a=commit;h=317c55c2d188595457d8f7983494e1ec10b6306b

Not sure that packages are already released, maybe in pvetest for now.

 

[ferociousmilkyway]

Just checked this, and I'm in the middle of backing up a running IO-thread flagged volume. This is awesome! Now I can schedule and forget my backups

Thanks!

 

[ferociousmilkyway]

In case anyone who is excited by this but isn't sure what version I'm running, here:

root@pve 03:23:28 ~ → pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.21-4-pve)
pve-manager: 6.0-11 (running version: 6.0-11/2140ef37)
pve-kernel-5.0: 6.0-11
pve-kernel-helper: 6.0-11
pve-kernel-4.15: 5.4-9
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.21-4-pve: 5.0.21-9
pve-kernel-5.0.21-3-pve: 5.0.21-7
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-3
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-7
libpve-guest-common-perl: 3.0-2
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.0-9
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-8
pve-cluster: 6.0-7
pve-container: 3.0-10
pve-docs: 6.0-8
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-4
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.1-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-13
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2
root@pve 03:24:05 ~ →

I'm a non-subscriber on the beta (?) branch.

 

[motox]

It turns out I was using an older PVE (pve-manager 6.0-4). Now I updated the system (no subscription) to newer (pve-manager 6.0-11, other packages seem the same as yours) and now it worked. Thanks a lot fellas!

 

[pablomart81]

Hello, When trying to make a backup, it does not give errors but the backup does not work, when it appears it excludes the disk. Do you know why it happens and how to solve it?


root@pve01-poz:~# vzdump 3000 --mode snapshot --dumpdir /mnt/pve/MEDIAAGENT_POZ/dump/ --node pve01-poz --remove 0 --compress zstd
INFO: starting new backup job: vzdump 3000 --compress zstd --dumpdir /mnt/pve/MEDIAAGENT_POZ/dump/ --mode snapshot --node pve01-poz --remove 0
INFO: Starting Backup of VM 3000 (qemu)
INFO: Backup started at 2021-11-08 16:14:06
INFO: status = running
INFO: VM Name: Bacula
INFO: exclude disk 'virtio0' 'Storage_Vms:vm-3000-disk-0' (backup=no)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating vzdump archive '/mnt/pve/MEDIAAGENT_POZ/dump/vzdump-qemu-3000-2021_11_08-16_14_06.vma.zst'
INFO: backup contains no disks
INFO: starting template backup
INFO: /usr/bin/vma create -v -c /mnt/pve/MEDIAAGENT_POZ/dump/vzdump-qemu-3000-2021_11_08-16_14_06.tmp/qemu-server.conf exec:zstd --rsyncable --threads=1 > /mnt/pve/MEDIAAGENT_POZ/dump/vzdump-qemu-3000-2021_11_08-16_14_06.vma.dat
INFO: archive file size: 0KB
INFO: Finished Backup of VM 3000 (00:00:00)
INFO: Backup finished at 2021-11-08 16:14:06
INFO: Backup job finished successfully

 

[pablomart81]

I have already found the problem, the assigned disk must have the option "Backup" checked