[SOLVED] Can't restore backup

[Jarek]

Log:

restore vma archive: zcat /mnt/pve/qnap/dump/vzdump-qemu-1191-2019_03_08-10_18_13.vma.gz | vma extract -v -r /var/tmp/vzdumptmp974517.fifo - /var/tmp/vzdumptmp974517
CFG: size: 591 name: qemu-server.conf
DEV: dev_id=1 size: 34359738368 devname: drive-scsi0
DEV: dev_id=2 size: 8589934592 devname: drive-scsi1
CTIME: Fri Mar  8 10:18:15 2019
new volume ID is 'vm-gd_vm:vm-1291-disk-0'
map 'drive-scsi0' to 'rbd:vm-gd/vm-1291-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/vm-gd_vm.keyring' (write zeros = 0)
new volume ID is 'vm-ssd_vm:vm-1291-disk-0'
Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/PVE/QemuServer.pm line 5950.
map 'drive-scsi1' to 'rbd:vm-ssd/vm-1291-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/vm-ssd_vm.keyring' (write zeros = 0)

** (process:974520): ERROR **: can't open file rbd:vm-ssd/vm-1291-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/vm-ssd_vm.keyring - Unknown driver ''
/bin/bash: line 1: 974519 Broken pipe             zcat /mnt/pve/qnap/dump/vzdump-qemu-1191-2019_03_08-10_18_13.vma.gz
     974520 Trace/breakpoint trap   | vma extract -v -r /var/tmp/vzdumptmp974517.fifo - /var/tmp/vzdumptmp974517
Removing image: 1% complete...
Removing image: 2% complete...
[...]
Removing image: 98% complete...
Removing image: 99% complete...
Removing image: 100% complete...done.
temporary volume 'vm-ssd_vm:vm-1291-disk-0' sucessfuly removed
2019-03-08 11:05:11.423084 7f5c727fc700 -1 librbd::image::RemoveRequest: 0x563975cffea0 check_image_watchers: image has watchers - not removing
Removing image: 0% complete...failed.
rbd: error: image still has watchers
unable to cleanup 'vm-gd_vm:vm-1291-disk-0' - error with cfs lock 'storage-vm-gd_vm': rbd rm 'vm-1291-disk-0' error: rbd: error: image still has watchers
no lock found trying to remove 'create'  lock

TASK ERROR: command 'set -o pipefail && zcat /mnt/pve/qnap/dump/vzdump-qemu-1191-2019_03_08-10_18_13.vma.gz | vma extract -v -r /var/tmp/vzdumptmp974517.fifo - /var/tmp/vzdumptmp974517' failed: exit code 133

And machine config:

agent: 1
balloon: 1024
bootdisk: scsi0
cores: 2
cpu: kvm64,flags=+pcid
ide2: none,media=cdrom
memory: 4096
name: psql1
net0: virtio=4A:CF:18:89:CF:B0,bridge=vmbr0,tag=4003
numa: 0
ostype: l26
scsi0: vm-gd_vm:vm-1191-disk-1,cache=writeback,discard=on,size=32G
scsi1: vm-ssd_vm:vm-1191-disk-0,cache=writeback,discard=on,size=8G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=6f04dffd-79bd-4e39-b00a-6baa8984d566
sockets: 2
tablet: 0
vga: qxl

Backup/restore won't work with more than one virtual drive?

 

[Jarek]

Restore to local-lvm don't work too.

restore vma archive: zcat /mnt/pve/qnap/dump/vzdump-qemu-1191-2019_03_08-10_18_13.vma.gz | vma extract -v -r /var/tmp/vzdumptmp988144.fifo - /var/tmp/vzdumptmp988144
CFG: size: 591 name: qemu-server.conf
DEV: dev_id=1 size: 34359738368 devname: drive-scsi0
DEV: dev_id=2 size: 8589934592 devname: drive-scsi1
CTIME: Fri Mar  8 10:18:15 2019
  Using default stripesize 64.00 KiB.
  Logical volume "vm-1291-disk-0" created.
new volume ID is 'local-lvm:vm-1291-disk-0'
map 'drive-scsi0' to '/dev/pve/vm-1291-disk-0' (write zeros = 0)
Use of uninitialized value $fmt in string ne at /usr/share/perl5/PVE/Storage/LvmThinPlugin.pm line 87.
Use of uninitialized value $fmt in concatenation (.) or string at /usr/share/perl5/PVE/Storage/LvmThinPlugin.pmline 87.
  Logical volume "vm-1291-disk-0" successfully removed
temporary volume 'local-lvm:vm-1291-disk-0' sucessfuly removed
no lock found trying to remove 'create'  lock
command 'set -o pipefail && zcat /mnt/pve/qnap/dump/vzdump-qemu-1191-2019_03_08-10_18_13.vma.gz | vma extract -v -r /var/tmp/vzdumptmp988144.fifo - /var/tmp/vzdumptmp988144' failed: unsupported format '' at /usr/share/perl5/PVE/Storage/LvmThinPlugin.pm line 87.

Update:
After unpack .vma, both disk images have a .raw extension:

-rw-r--r-- 1 root root  32G mar  8 12:54 disk-drive-scsi0.raw
-rw-r--r-- 1 root root 8,0G mar  8 12:54 disk-drive-scsi1.raw
-rw-r--r-- 1 root root  591 mar  8 12:54 qemu-server.conf

But, one image is encrypted and haven't a partition table:

Disk disk-drive-scsi1.raw: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Can this be the reason why the image format is not recognized?

 

[Stoiko Ivanov]

Which versions are you running? (pveversion -v)?

 

[Jarek]

proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
pve-manager: 5.2-8 (running version: 5.2-8/fdf39912)
pve-kernel-4.15: 5.2-7
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-1-pve: 4.15.18-19
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.13.16-2-pve: 4.13.16-48
pve-kernel-4.13.13-2-pve: 4.13.13-33
ceph: 12.2.8-pve1
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-27
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-19
pve-cluster: 5.0-30
pve-container: 2.0-26
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-33
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

 

[Stoiko Ivanov]

Please upgrade to the latest version!

This bug was fixed with a newer version of the pve-packages

 

[Jarek]

Upgrade proxmox fixes the problem.
Thank you.