cant restore a VM from a backup

L

londibm

New Member
Jan 16, 2025
4
0
1
Hello,
I have a backup of a vm that in the log finished OK
2025-01-05 08:36:48 INFO: 100% (200.0 GiB of 200.0 GiB) in 1d 12h 8m 58s, read: 192.8 MiB/s, write: 2.2 MiB/s 2025-01-05 08:36:48 INFO: backup is sparse: 35.85 GiB (17%) total zero data 2025-01-05 08:36:48 INFO: transferred 200.00 GiB in 130138 seconds (1.6 MiB/s) 2025-01-05 08:36:48 INFO: stopping kvm after backup task 2025-01-05 08:36:54 INFO: archive file size: 86.14GB 2025-01-05 08:36:54 INFO: adding notes to backup 2025-01-05 08:36:54 INFO: Finished Backup of VM 101 (36:09:06)

but when trying to restore I get this error :
Could not extract backed up config: Failed to extract config from VMA archive: zstd: /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst: unsupported format Skipping early checks!restore vma archive: zstd -q -d -c /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst | vma extract -v -r /var/tmp/vzdumptmp2048291.fifo - /var/tmp/vzdumptmp2048291error before or during data restore, some or all disks were not completely restored. VM 101 state is NOT cleaned up.TASK ERROR: command 'set -o pipefail && zstd -q -d -c /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst | vma extract -v -r /var/tmp/vzdumptmp2048291.fifo - /var/tmp/vzdumptmp2048291' failed: got timeout reading VMA header - corrupted?

is there any way I can still use this backup?
 
proxmox-ve: 8.3.0 (running kernel: 6.5.13-6-pve)
pve-manager: 8.3.2 (running version: 8.3.2/3e76eec21c4a14a7)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
ceph: 18.2.4-pve3
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-2
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.3
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
 
londibm said:
qemu-server: 8.3.3
Click to expand...
Good, so the increased timeout is already contained!

londibm said:
100% (200.0 GiB of 200.0 GiB) in 1d 12h 8m 58s, read: 192.8 MiB/s, write: 2.2 MiB/s
Click to expand...
So this seems to be a rather slow storage? What storage backend is this? Maybe you can transfer the backup to local storage first and try restoring from there?
 
I have alreay copied to a newer ssd all the data that was on that drive, but still same error.
 
What is the output of zstd -dc /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst | vma config -? Adapt the path to the current location of your backup archive if necessary.

Edit: fixed typo
 
Last edited:
this is the out put
root@pve:~# zstd -dc /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst
zstd: /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst: unsupported format
root@pve:~# zstd -dc /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst | vma config -
zstd: /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst: unsupported format
vma: can't read vma header - got EOF
Trace/breakpoint trap
 
Given the outputs, I am afraid the archive is corrupt indeed. It is not an issue with the timeout.
 
  • Like
Reactions: fiona
Hi,
londibm said:
this is the out put
root@pve:~# zstd -dc /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst
zstd: /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst: unsupported format
root@pve:~# zstd -dc /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst | vma config -
zstd: /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst: unsupported format
vma: can't read vma header - got EOF
Trace/breakpoint trap
Click to expand...
what do the following commands say?
Code: 
file /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst
hexdump -n 512 -c /mnt/nv0/dump/vzdump-qemu-101-2025_01_03-20_27_48.vma.zst
 
You must log in or register to reply here.
Top Bottom