Yup ... on all nodes. So file restore is not currently working on actual version proxmox-backup-file-restore: 2.0.5-2.
?
No, at the "place" the error happens those two had no effect whatsoever, but I'll look into it.
proxmox-backup-file-restore version 2.0.7-1 available on pvetest repository at time of writing, as the update is rather small and contained we may move it to no-subscription soon, it only broke there.proxmox-ve: 7.0-2 (running kernel: 5.11.22-3-pve)
pve-manager: 7.0-10 (running version: 7.0-10/d2f465d3)
pve-kernel-5.11: 7.0-6
pve-kernel-helper: 7.0-6
pve-kernel-5.4: 6.4-5
pve-kernel-5.11.22-3-pve: 5.11.22-6
pve-kernel-5.4.128-1-pve: 5.4.128-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.17-1-pve: 4.15.17-9
ceph-fuse: 14.2.21-1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.2.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-5
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-9
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.7-1
proxmox-backup-file-restore: 2.0.7-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-8
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-11
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1Which version are you on? (
pveversion -v) Are you sure the filesystem on the backup is valid and readable? The error itself only says that mounting failed. You can also check the log of the last file-restore at /var/log/proxmox-backup/file-restore/qemu.log.
Proxmox-file-restore failed: Error: Starting VM failed. See output above for more information. (500)# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.4: 6.4-6
pve-kernel-5.11.22-4-pve: 5.11.22-8
pve-kernel-5.4.140-1-pve: 5.4.140-1
pve-kernel-5.4.128-1-pve: 5.4.128-2
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph: 16.2.5-pve1
ceph-fuse: 16.2.5-pve1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-6
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-11
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-3
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1# cat /var/log/proxmox-backup/file-restore/qemu.log
[2021-09-20T15:50:02+02:00] PBS file restore VM logproxmox-file-restore list vm/100/2021-09-20T16:20:30Z /drive-scsi0.img.fidx/ --repository root@pam@127.0.0.1:datastoreI tried this:
export PBS_PASSWORD="MyPassword"
export PBS_REPOSITORY="backup@pbs@MyIpAddress:storage1"
proxmox-file-restore list vm/105/2021-09-20T13:28:53Z /drive-virtio0.img.fidx/certificate validation failed - Certificate fingerprint was not confirmed.
qemu-system-x86_64: -drive file=pbs:repository=backup@pbs@10.255.253.200:8007:storage1,,snapshot=vm/105/2021-09-20T13:28:53Z,,archive=drive-virtio0.img.fidx,read-only=on,if=none,id=drive0: PBS connect failed: command error: error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1913:
Error: Starting VM failed. See output above for more information.You need to export
PBS_FINGERPRINT=00:00:00... as well, with the fingerprint shown on the front page of your PBS install, or use a certificate that is in the system trust store.Thank's Stefan for the suggestion, now executing proxmox-file-restore exit this message:
CID '10' in use by other VM, attempting next one
CID '11' in use by other VM, attempting next one
CID '12' in use by other VM, attempting next one
Error: starting VM timed outHi Stefan,
proxmox-file-restore list ct/150/2021-09-21T12:54:01Zexport PBS_REPOSITORY=localhost:backup1
export PBS_PASSWORD=3E.............
export PBS_FINGERPRINT=9b:94:d8:8c:5e:bc:.........
--
pbs user: root@pamIt does, you need to append the folder you want to list. For starters, just try root
/. If that doesn't help, what error message are you getting?root@srv:~# proxmox-file-restore extract ct/150/2021-09-21T12:54:01Z /root.pxar.didx/*.orig /root/origs/ --verbose
Error: error opening '[47, 114, 111, 111, 116, 47, 42, 46, 111, 114, 105, 103]'Would make sense as a feature request for VM restore, though at least you can restore entire folders. For CTs this is already possible via the normal 'proxmox-backup-client' restore method, see here: https://pbs.proxmox.com/docs/backup-client.html#restoring-data
pxar:/ > list-selected
/root/chattrtest
/root/chattrtest/immut2.txt
pxar:/ > restore-selected /usr/temp/pxartest
Error: failed to create file "immut2.txt": EEXIST: File existsNot at the moment, but you could work around by extracting to a seperate folder and using rsync (with
--delete) to merge them.