Backup of VM 62002 failed - VM qmp command 'query-pbs-bitmap-info' failed

L

lfl

New Member
May 7, 2022
2
0
1
Hello Team,

I have some problem when i try to save a vm with pbs after this update 02 May 2022
the problem is only for vm with some rbd snap

Update of pve server

Start-Date: 2022-05-02 16:30:49
Commandline: apt --yes dist-upgrade
Requested-By: admin (1000)

Upgrade: proxmox-widget-toolkit:amd64 (3.4-7, 3.4-10), libpve-rs-perl:amd64 (0.6.0, 0.6.1), pve-firmware:amd64 (3.3-6, 3.4-1), tzdata:amd64 (2021a-1+deb11u2, 2021a-1+deb11u3), zfs-zed:amd64 (2.1.2-pve1, 2.1.4-pve1), pve-qemu-kvm:amd64 (6.1.1-2, 6.2.0-5), libnvpair3linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libproxmox-acme-perl:amd64 (1.4.1, 1.4.2), pve-ha-manager:amd64 (3.3-3, 3.3-4), lxcfs:amd64 (4.0.11-pve1, 4.0.12-pve1), libuutil3linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libpve-storage-perl:amd64 (7.1-1, 7.1-2), libzpool5linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libpve-guest-common-perl:amd64 (4.1-1, 4.1-2), proxmox-ve:amd64 (7.1-1, 7.1-2), lxc-pve:amd64 (4.0.11-1, 4.0.12-1), novnc-pve:amd64 (1.3.0-2, 1.3.0-3), proxmox-backup-file-restore:amd64 (2.1.5-1, 2.1.6-1), qemu-server:amd64 (7.1-4, 7.1-5), libpve-access-control:amd64 (7.1-6, 7.1-7), pve-container:amd64 (4.1-4, 4.1-5), libproxmox-acme-plugins:amd64 (1.4.1, 1.4.2), pve-i18n:amd64 (2.6-2, 2.6-3), proxmox-backup-client:amd64 (2.1.5-1, 2.1.6-1), smartmontools:amd64 (7.2-pve2, 7.2-pve3), pve-kernel-5.13.19-6-pve:amd64 (5.13.19-14, 5.13.19-15), pve-manager:amd64 (7.1-11, 7.1-12), libzfs4linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libpve-u2f-server-perl:amd64 (1.1-1, 1.1-2), pve-kernel-helper:amd64 (7.1-13, 7.2-2), zfsutils-linux:amd64 (2.1.2-pve1, 2.1.4-pve1)
End-Date: 2022-05-02 16:34:54

i do dist-upgrade this morning , i got the same problem

proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-1-pve: 5.15.35-2
pve-kernel-5.13.19-6-pve: 5.13.19-15
ceph: 16.2.7
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksmtuned: 4.20150326
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u1
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1


Upadate of pbs server
Start-Date: 2022-05-02 16:34:30
Commandline: apt --yes dist-upgrade
Install: pve-kernel-5.13.19-6-pve:amd64 (5.13.19-15, automatic)
Upgrade: udev:amd64 (247.3-6, 247.3-7), bind9-host:amd64 (1:9.16.22-1~deb11u1, 1:9.16.27-1~deb11u1), proxmox-widget-toolkit:amd64 (3.4-5, 3.4-9), pve-firmware:amd64 (3.3-5, 3.4-1), gpg:amd64 (2.2.27-2, 2.2.27-2+deb11u1), tzdata:amd64 (2021a-1+deb11u2, 2021a-1+deb11u3), zfs-zed:amd64 (2.1.2-pve1, 2.1.4-pve1), chrony:amd64 (4.0-8+deb11u1, 4.0-8+deb11u2), libpam-systemd:amd64 (247.3-6, 247.3-7), zfs-initramfs:amd64 (2.1.2-pve1, 2.1.4-pve1), libarchive13:amd64 (3.4.3-2+b1, 3.4.3-2+deb11u1), liblzma5:amd64 (5.2.5-2, 5.2.5-2.1~deb11u1), spl:amd64 (2.1.2-pve1, 2.1.4-pve1), libnvpair3linux:amd64 (2.1.2-pve1, 2.1.4-pve1), tasksel-data:amd64 (3.68, 3.68+deb11u1), libsasl2-2:amd64 (2.1.27+dfsg-2.1, 2.1.27+dfsg-2.1+deb11u1), libexpat1:amd64 (2.2.10-2, 2.2.10-2+deb11u3), libuutil3linux:amd64 (2.1.2-pve1, 2.1.4-pve1), tasksel:amd64 (3.68, 3.68+deb11u1), libsystemd0:amd64 (247.3-6, 247.3-7), libzpool5linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libnss-systemd:amd64 (247.3-6, 247.3-7), gnupg:amd64 (2.2.27-2, 2.2.27-2+deb11u1), libsasl2-modules-db:amd64 (2.1.27+dfsg-2.1, 2.1.27+dfsg-2.1+deb11u1), gpg-wks-server:amd64 (2.2.27-2, 2.2.27-2+deb11u1), libxml2:amd64 (2.9.10+dfsg-6.7, 2.9.10+dfsg-6.7+deb11u1), xz-utils:amd64 (5.2.5-2, 5.2.5-2.1~deb11u1), systemd:amd64 (247.3-6, 247.3-7), libudev1:amd64 (247.3-6, 247.3-7), gpg-agent:amd64 (2.2.27-2, 2.2.27-2+deb11u1), libc6:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), locales:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), gpgv:amd64 (2.2.27-2, 2.2.27-2+deb11u1), bind9-dnsutils:amd64 (1:9.16.22-1~deb11u1, 1:9.16.27-1~deb11u1), base-files:amd64 (11.1+deb11u2, 11.1+deb11u3), gzip:amd64 (1.10-4, 1.10-4+deb11u1), gpgsm:amd64 (2.2.27-2, 2.2.27-2+deb11u1), proxmox-backup-client:amd64 (2.1.5-1, 2.1.6-1), smartmontools:amd64 (7.2-1, 7.2-pve3), libssl1.1:amd64 (1.1.1k-1+deb11u1, 1.1.1n-0+deb11u1), libc-l10n:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), btrfs-progs:amd64 (5.10.1-2, 5.16.2-1~bpo11+1), bind9-libs:amd64 (1:9.16.22-1~deb11u1, 1:9.16.27-1~deb11u1), libc-bin:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), pve-kernel-5.13:amd64 (7.1-7, 7.1-9), dirmngr:amd64 (2.2.27-2, 2.2.27-2+deb11u1), libzfs4linux:amd64 (2.1.2-pve1, 2.1.4-pve1), systemd-sysv:amd64 (247.3-6, 247.3-7), gnupg-utils:amd64 (2.2.27-2, 2.2.27-2+deb11u1), sysvinit-utils:amd64 (2.96-7, 2.96-7+deb11u1), gnupg-l10n:amd64 (2.2.27-2, 2.2.27-2+deb11u1), gpg-wks-client:amd64 (2.2.27-2, 2.2.27-2+deb11u1), zlib1g:amd64 (1:1.2.11.dfsg-2, 1:1.2.11.dfsg-2+deb11u1), proxmox-backup-docs:amd64 (2.1.5-1, 2.1.6-1), proxmox-backup-server:amd64 (2.1.5-1, 2.1.6-1), gpgconf:amd64 (2.2.27-2, 2.2.27-2+deb11u1), pve-kernel-helper:amd64 (7.1-10, 7.2-1), zfsutils-linux:amd64 (2.1.2-pve1, 2.1.4-pve1), openssl:amd64 (1.1.1k-1+deb11u1, 1.1.1n-0+deb11u1)
End-Date: 2022-05-02 16:35:38


Have got this error now
INFO: starting new backup job: vzdump 62002 --storage default.pbs.server --remove 0 --notes-template '{{guestname}}' --node node --mode stop
INFO: Starting Backup of VM 62002 (qemu)
INFO: Backup started at 2022-05-07 17:13:18
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: samba
INFO: include disk 'virtio0' 'default.rbd.debian:vm-62002-disk-1' 64G
INFO: include disk 'virtio1' 'default.rbd.data:vm-62002-disk-0' 100T
INFO: include disk 'efidisk0' 'local:62002/vm-62002-disk-0.qcow2' 128K
INFO: creating Proxmox Backup Server archive 'vm/62002/2022-05-07T15:13:18Z'
INFO: starting kvm to execute backup task
INFO: enabling encryption
INFO: started backup task '16504b97-3995-41be-8779-6ce11f8886de'
ERROR: VM 62002 qmp command 'query-pbs-bitmap-info' failed - unable to connect to VM 62002 qmp socket - timeout after 31 retries
INFO: aborting backup job
ERROR: VM 62002 qmp command 'backup-cancel' failed - got timeout
VM 62002 qmp command 'query-status' failed - unable to connect to VM 62002 qmp socket - timeout after 31 retries
ERROR: Backup of VM 62002 failed - VM 62002 qmp command 'query-pbs-bitmap-info' failed - unable to connect to VM 62002 qmp socket - timeout after 31 retries
INFO: Failed at 2022-05-07 17:25:20
INFO: Backup job finished with errors
TASK ERROR: job errors

rbd snap list default.rbd.debian/vm-62002-disk-1
SNAPID NAME SIZE PROTECTED TIMESTAMP
113 vm-62002-disk-1-20220305-190000 64 GiB Sat Mar 5 19:00:04 2022
125 vm-62002-disk-1-20220312-190000 64 GiB Sat Mar 12 19:00:05 2022
127 vm-62002-disk-1-20220319-190000 64 GiB Sat Mar 19 19:00:03 2022
129 vm-62002-disk-1-20220326-190000 64 GiB Sat Mar 26 19:00:03 2022
131 vm-62002-disk-1-20220402-190000 64 GiB Sat Apr 2 19:00:05 2022
141 vm-62002-disk-1-20220409-190000 64 GiB Sat Apr 9 19:00:04 2022
143 vm-62002-disk-1-20220416-190000 64 GiB Sat Apr 16 19:00:05 2022
145 vm-62002-disk-1-20220423-190000 64 GiB Sat Apr 23 19:00:04 2022
147 vm-62002-disk-1-20220430-190000 64 GiB Sat Apr 30 19:00:05 2022

rbd snap list default.rbd.data/vm-62002-disk-0
SNAPID NAME SIZE PROTECTED TIMESTAMP
41 vm-62002-disk-0-20220305-190000 100 TiB Sat Mar 5 19:00:06 2022
47 vm-62002-disk-0-20220312-190000 100 TiB Sat Mar 12 19:00:06 2022
48 vm-62002-disk-0-20220319-190000 100 TiB Sat Mar 19 19:00:05 2022
49 vm-62002-disk-0-20220326-190000 100 TiB Sat Mar 26 19:00:05 2022
50 vm-62002-disk-0-20220402-190000 100 TiB Sat Apr 2 19:00:06 2022
55 vm-62002-disk-0-20220409-190000 100 TiB Sat Apr 9 19:00:05 2022
56 vm-62002-disk-0-20220416-190000 100 TiB Sat Apr 16 19:00:06 2022
57 vm-62002-disk-0-20220423-190000 100 TiB Sat Apr 23 19:00:06 2022
58 vm-62002-disk-0-20220430-190000 100 TiB Sat Apr 30 19:00:07 2022

Before this update, no problems with proxmox-backup server and vm with "rbd snap"
Thanks in advance for your reply
Best Regards
 
Hi lfl

A few hours ago I had a windows VM, with 3 disks (qcow2,scsi,virtio), the vm had been backing up correctly for months.
And today reading that SQL SERVER needs RAW disks for better performance I decided to remove 2 of 3 disks and add new RAW disks.

When trying to do the backup in PBS I noticed similar errors:
1652842878905.png

So later I removed the RAW disks again and added new ones but this time as: Virtio SCSI, qcow2, SSD+discard, IO thread.

And I tried again the backup and this one is performing:
1652842837945.png

This is the content backup:
1652843261273.png

A few months ago a friend had advised me against using RAW disks for backups in PBS; I had forgotten about it, now I see why.

So, my experience so far is that I can only back up RAW disks locally on Proxmox; which is no longer possible because the storage is now in a Proxmox+NAS+PBS cluster.

Hopefully this helps you in some way.
I haven't upgraded to 7.2 yet

Regards
 
  • Like
Reactions: lfl
Hi,
lfl said:
Hello Team,

I have some problem when i try to save a vm with pbs after this update 02 May 2022
the problem is only for vm with some rbd snap

Update of pve server

Start-Date: 2022-05-02 16:30:49
Commandline: apt --yes dist-upgrade
Requested-By: admin (1000)

Upgrade: proxmox-widget-toolkit:amd64 (3.4-7, 3.4-10), libpve-rs-perl:amd64 (0.6.0, 0.6.1), pve-firmware:amd64 (3.3-6, 3.4-1), tzdata:amd64 (2021a-1+deb11u2, 2021a-1+deb11u3), zfs-zed:amd64 (2.1.2-pve1, 2.1.4-pve1), pve-qemu-kvm:amd64 (6.1.1-2, 6.2.0-5), libnvpair3linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libproxmox-acme-perl:amd64 (1.4.1, 1.4.2), pve-ha-manager:amd64 (3.3-3, 3.3-4), lxcfs:amd64 (4.0.11-pve1, 4.0.12-pve1), libuutil3linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libpve-storage-perl:amd64 (7.1-1, 7.1-2), libzpool5linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libpve-guest-common-perl:amd64 (4.1-1, 4.1-2), proxmox-ve:amd64 (7.1-1, 7.1-2), lxc-pve:amd64 (4.0.11-1, 4.0.12-1), novnc-pve:amd64 (1.3.0-2, 1.3.0-3), proxmox-backup-file-restore:amd64 (2.1.5-1, 2.1.6-1), qemu-server:amd64 (7.1-4, 7.1-5), libpve-access-control:amd64 (7.1-6, 7.1-7), pve-container:amd64 (4.1-4, 4.1-5), libproxmox-acme-plugins:amd64 (1.4.1, 1.4.2), pve-i18n:amd64 (2.6-2, 2.6-3), proxmox-backup-client:amd64 (2.1.5-1, 2.1.6-1), smartmontools:amd64 (7.2-pve2, 7.2-pve3), pve-kernel-5.13.19-6-pve:amd64 (5.13.19-14, 5.13.19-15), pve-manager:amd64 (7.1-11, 7.1-12), libzfs4linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libpve-u2f-server-perl:amd64 (1.1-1, 1.1-2), pve-kernel-helper:amd64 (7.1-13, 7.2-2), zfsutils-linux:amd64 (2.1.2-pve1, 2.1.4-pve1)
End-Date: 2022-05-02 16:34:54

i do dist-upgrade this morning , i got the same problem

proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-1-pve: 5.15.35-2
pve-kernel-5.13.19-6-pve: 5.13.19-15
ceph: 16.2.7
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksmtuned: 4.20150326
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u1
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1


Upadate of pbs server
Start-Date: 2022-05-02 16:34:30
Commandline: apt --yes dist-upgrade
Install: pve-kernel-5.13.19-6-pve:amd64 (5.13.19-15, automatic)
Upgrade: udev:amd64 (247.3-6, 247.3-7), bind9-host:amd64 (1:9.16.22-1~deb11u1, 1:9.16.27-1~deb11u1), proxmox-widget-toolkit:amd64 (3.4-5, 3.4-9), pve-firmware:amd64 (3.3-5, 3.4-1), gpg:amd64 (2.2.27-2, 2.2.27-2+deb11u1), tzdata:amd64 (2021a-1+deb11u2, 2021a-1+deb11u3), zfs-zed:amd64 (2.1.2-pve1, 2.1.4-pve1), chrony:amd64 (4.0-8+deb11u1, 4.0-8+deb11u2), libpam-systemd:amd64 (247.3-6, 247.3-7), zfs-initramfs:amd64 (2.1.2-pve1, 2.1.4-pve1), libarchive13:amd64 (3.4.3-2+b1, 3.4.3-2+deb11u1), liblzma5:amd64 (5.2.5-2, 5.2.5-2.1~deb11u1), spl:amd64 (2.1.2-pve1, 2.1.4-pve1), libnvpair3linux:amd64 (2.1.2-pve1, 2.1.4-pve1), tasksel-data:amd64 (3.68, 3.68+deb11u1), libsasl2-2:amd64 (2.1.27+dfsg-2.1, 2.1.27+dfsg-2.1+deb11u1), libexpat1:amd64 (2.2.10-2, 2.2.10-2+deb11u3), libuutil3linux:amd64 (2.1.2-pve1, 2.1.4-pve1), tasksel:amd64 (3.68, 3.68+deb11u1), libsystemd0:amd64 (247.3-6, 247.3-7), libzpool5linux:amd64 (2.1.2-pve1, 2.1.4-pve1), libnss-systemd:amd64 (247.3-6, 247.3-7), gnupg:amd64 (2.2.27-2, 2.2.27-2+deb11u1), libsasl2-modules-db:amd64 (2.1.27+dfsg-2.1, 2.1.27+dfsg-2.1+deb11u1), gpg-wks-server:amd64 (2.2.27-2, 2.2.27-2+deb11u1), libxml2:amd64 (2.9.10+dfsg-6.7, 2.9.10+dfsg-6.7+deb11u1), xz-utils:amd64 (5.2.5-2, 5.2.5-2.1~deb11u1), systemd:amd64 (247.3-6, 247.3-7), libudev1:amd64 (247.3-6, 247.3-7), gpg-agent:amd64 (2.2.27-2, 2.2.27-2+deb11u1), libc6:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), locales:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), gpgv:amd64 (2.2.27-2, 2.2.27-2+deb11u1), bind9-dnsutils:amd64 (1:9.16.22-1~deb11u1, 1:9.16.27-1~deb11u1), base-files:amd64 (11.1+deb11u2, 11.1+deb11u3), gzip:amd64 (1.10-4, 1.10-4+deb11u1), gpgsm:amd64 (2.2.27-2, 2.2.27-2+deb11u1), proxmox-backup-client:amd64 (2.1.5-1, 2.1.6-1), smartmontools:amd64 (7.2-1, 7.2-pve3), libssl1.1:amd64 (1.1.1k-1+deb11u1, 1.1.1n-0+deb11u1), libc-l10n:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), btrfs-progs:amd64 (5.10.1-2, 5.16.2-1~bpo11+1), bind9-libs:amd64 (1:9.16.22-1~deb11u1, 1:9.16.27-1~deb11u1), libc-bin:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), pve-kernel-5.13:amd64 (7.1-7, 7.1-9), dirmngr:amd64 (2.2.27-2, 2.2.27-2+deb11u1), libzfs4linux:amd64 (2.1.2-pve1, 2.1.4-pve1), systemd-sysv:amd64 (247.3-6, 247.3-7), gnupg-utils:amd64 (2.2.27-2, 2.2.27-2+deb11u1), sysvinit-utils:amd64 (2.96-7, 2.96-7+deb11u1), gnupg-l10n:amd64 (2.2.27-2, 2.2.27-2+deb11u1), gpg-wks-client:amd64 (2.2.27-2, 2.2.27-2+deb11u1), zlib1g:amd64 (1:1.2.11.dfsg-2, 1:1.2.11.dfsg-2+deb11u1), proxmox-backup-docs:amd64 (2.1.5-1, 2.1.6-1), proxmox-backup-server:amd64 (2.1.5-1, 2.1.6-1), gpgconf:amd64 (2.2.27-2, 2.2.27-2+deb11u1), pve-kernel-helper:amd64 (7.1-10, 7.2-1), zfsutils-linux:amd64 (2.1.2-pve1, 2.1.4-pve1), openssl:amd64 (1.1.1k-1+deb11u1, 1.1.1n-0+deb11u1)
End-Date: 2022-05-02 16:35:38


Have got this error now
INFO: starting new backup job: vzdump 62002 --storage default.pbs.server --remove 0 --notes-template '{{guestname}}' --node node --mode stop
INFO: Starting Backup of VM 62002 (qemu)
INFO: Backup started at 2022-05-07 17:13:18
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: samba
INFO: include disk 'virtio0' 'default.rbd.debian:vm-62002-disk-1' 64G
INFO: include disk 'virtio1' 'default.rbd.data:vm-62002-disk-0' 100T
INFO: include disk 'efidisk0' 'local:62002/vm-62002-disk-0.qcow2' 128K
INFO: creating Proxmox Backup Server archive 'vm/62002/2022-05-07T15:13:18Z'
INFO: starting kvm to execute backup task
INFO: enabling encryption
INFO: started backup task '16504b97-3995-41be-8779-6ce11f8886de'
ERROR: VM 62002 qmp command 'query-pbs-bitmap-info' failed - unable to connect to VM 62002 qmp socket - timeout after 31 retries
INFO: aborting backup job
ERROR: VM 62002 qmp command 'backup-cancel' failed - got timeout
VM 62002 qmp command 'query-status' failed - unable to connect to VM 62002 qmp socket - timeout after 31 retries
ERROR: Backup of VM 62002 failed - VM 62002 qmp command 'query-pbs-bitmap-info' failed - unable to connect to VM 62002 qmp socket - timeout after 31 retries
INFO: Failed at 2022-05-07 17:25:20
INFO: Backup job finished with errors
TASK ERROR: job errors

rbd snap list default.rbd.debian/vm-62002-disk-1
SNAPID NAME SIZE PROTECTED TIMESTAMP
113 vm-62002-disk-1-20220305-190000 64 GiB Sat Mar 5 19:00:04 2022
125 vm-62002-disk-1-20220312-190000 64 GiB Sat Mar 12 19:00:05 2022
127 vm-62002-disk-1-20220319-190000 64 GiB Sat Mar 19 19:00:03 2022
129 vm-62002-disk-1-20220326-190000 64 GiB Sat Mar 26 19:00:03 2022
131 vm-62002-disk-1-20220402-190000 64 GiB Sat Apr 2 19:00:05 2022
141 vm-62002-disk-1-20220409-190000 64 GiB Sat Apr 9 19:00:04 2022
143 vm-62002-disk-1-20220416-190000 64 GiB Sat Apr 16 19:00:05 2022
145 vm-62002-disk-1-20220423-190000 64 GiB Sat Apr 23 19:00:04 2022
147 vm-62002-disk-1-20220430-190000 64 GiB Sat Apr 30 19:00:05 2022

rbd snap list default.rbd.data/vm-62002-disk-0
SNAPID NAME SIZE PROTECTED TIMESTAMP
41 vm-62002-disk-0-20220305-190000 100 TiB Sat Mar 5 19:00:06 2022
47 vm-62002-disk-0-20220312-190000 100 TiB Sat Mar 12 19:00:06 2022
48 vm-62002-disk-0-20220319-190000 100 TiB Sat Mar 19 19:00:05 2022
49 vm-62002-disk-0-20220326-190000 100 TiB Sat Mar 26 19:00:05 2022
50 vm-62002-disk-0-20220402-190000 100 TiB Sat Apr 2 19:00:06 2022
55 vm-62002-disk-0-20220409-190000 100 TiB Sat Apr 9 19:00:05 2022
56 vm-62002-disk-0-20220416-190000 100 TiB Sat Apr 16 19:00:06 2022
57 vm-62002-disk-0-20220423-190000 100 TiB Sat Apr 23 19:00:06 2022
58 vm-62002-disk-0-20220430-190000 100 TiB Sat Apr 30 19:00:07 2022

Before this update, no problems with proxmox-backup server and vm with "rbd snap"
Thanks in advance for your reply
Best Regards
Click to expand...
please see this thread which is likely about the same issue for more information and workarounds.
 
  • Like
Reactions: lfl
Hi

mrE & Fabian_E​

i will try to change driver virtio to scsi and add ssd option
and take a look to the thread

Thank you for your reply ;)
Best Regards
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom