File Restore not possible

philipl · May 23, 2022

Hey together

I just connected my Proxmox Backup Server (version 2.2) to my PVE (pve-manager/7.2-3).
Backupping works just fine, but every time I try to restore single files I receive following error message:

proxmox-file-restore failed: Error: Starting VM failed. See output above for more information. (500)

Any idea what causes this error?
If any further information is needed, I will provide it of course.

BR

Matthias. · May 23, 2022

well, what is the output above mentioned in the error message? : )

philipl · May 23, 2022

I do not see any

Matthias. said:
well, what is the output above mentioned in the error message? : )

I do not see any

In the task-section there is nothing displayed either:

Matthias. · May 23, 2022

So, no information at all that in the task log? Please also check the PBS logs.
Also take a look at the server status. Were the pbs out of ram when you did the restore?

philipl · May 23, 2022

Matthias. said:
So, no information at all that in the task log? Please also check the PBS logs.
Also take a look at the server status. Were the pbs out of ram when you did the restore?

within the PBS task-log I received this log:

RAM on the PBS looks Ok as well. It has 4GB RAM and there is not other Task running.

BR

foxx · May 31, 2022

hi!

I have the same issue right now on stand alone pve - on a cluste the file restore still works.

BR,
Patrick

dcsapak · Jun 1, 2022

please check the logs in '/var/log/proxmox-backup/file-restore/qemu.log' on the pve node

foxx · Jun 1, 2022

Hey Dominik,

not saying much:

Code:

root@pve92:~# cat /var/log/proxmox-backup/file-restore/qemu.log
[2022-06-01T08:56:46+02:00] PBS file restore VM log

BR,
Patrick

dcsapak · Jun 1, 2022

you could try to invoke the 'proxmox-file-restore' commands manually, this should give more output (hopefully)

foxx · Jun 1, 2022

Hey Dominik,

if you can tell me, what exactly to do, of cause... I'm struggling with the exact parameters... I can see the snapshots with the backup-client, but I'm not aware how I can do a restore from command line.

Code:

root@pve92:~# proxmox-backup-client list --repository pve92@pbs@xxx:8007:pbs-backup1
Password for "pve92@pbs": ****************
┌────────┬─────────────────────────────┬──────────────┬────────────────────────────────────────────────────────┐
│ group  │ last snapshot               │ backup-count │ files                                                  │
╞════════╪═════════════════════════════╪══════════════╪════════════════════════════════════════════════════════╡
│ vm/187 │ vm/187/2022-05-31T22:00:04Z │            3 │ client.log drive-scsi0.img index.json qemu-server.conf │
└────────┴─────────────────────────────┴──────────────┴────────────────────────────────────────────────────────┘

BR,
Patrick

dcsapak · Jun 1, 2022

check the 'proxmox-file-restore' command e.g. the manpage: 'man proxmox-file-restore'
there is a 'list' and 'extract' command

e.g.

Code:

proxmox-file-restore list <snapshot> <path> --repository <repository>

i'd start with the path '/' and then work your way forward until you get an error (if you get one)

foxx · Jun 1, 2022

HI Dominik,

ah, okay:

Code:

root@pve92:~# proxmox-file-restore list vm/187/2022-05-31T22:00:04Z / --repository pve92@pbs@xxx:8007:pbs-backup1
Password for "pve92@pbs": ****************
┌──────┬──────────────────────┬───────────────┬───────────────┐
│ type │ name                 │ last modified │          size │
╞══════╪══════════════════════╪═══════════════╪═══════════════╡
│ v    │ drive-scsi0.img.fidx │               │ 2147483648000 │
└──────┴──────────────────────┴───────────────┴───────────────┘
root@pve92:~# proxmox-file-restore list vm/187/2022-05-31T22:00:04Z /drive-scsi0.img.fidx --repository pve92@pbs@xxx.cc:8007:pbs-backup1
Error: environment variable PBS_PASSWORD has to be set for QEMU VM restore
root@pve92:~# export PBS_PASSWORD=xxx
root@pve92:~# proxmox-file-restore list vm/187/2022-05-31T22:00:04Z /drive-scsi0.img.fidx --repository pve92@pbs@xxx:8007:pbs-backup1
qemu-system-x86_64: -device vhost-vsock-pci,guest-cid=10,disable-legacy=on: vhost-vsock: failed to open vhost device: No such device
Error: Starting VM failed. See output above for more information.

dcsapak · Jun 1, 2022

can you post your 'pveversion -v' ?

foxx · Jun 1, 2022

Sure:

Code:

root@pve92:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.11.22-3-pve)
pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc)
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-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-4
libqb0: 1.0.5-1
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
proxmox-backup-client: 2.2.1-1
proxmox-backup-file-restore: 2.2.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
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-2
pve-qemu-kvm: 6.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

dcsapak · Jun 1, 2022

look pretty normal, aside from the fact that you did not reboot since a long time (or did you intentionally boot into the 5.11 kernel?)\

EDIT: seems someone else had the same problem and a reboot fixed it: https://forum.proxmox.com/threads/file-restore-not-working-strange-errormessage.103350/

foxx · Jun 1, 2022

hi!
Yes, the old kernel was the problem. I thought I already rebooted the server, but this was another one.

Thanks!
Patrick

philipl · Jun 22, 2022

I still have this issue

Rebootet the host and the pbs. The host is inside a cluster - should the whole cluster be rebooted?

dcsapak · Jun 22, 2022

philipl said:
Rebootet the host and the pbs. The host is inside a cluster - should the whole cluster be rebooted?

that should not be necessary as it does nothing for that issue..
can you post your pbs & pve versions?

EDIT: add '& pve'
EDIT2: after thinking, which host did you reboot? for the file restore, the host where you connect to is relevant, not where the target vm is

philipl · Jun 22, 2022

Thanks for your fast reply!

I rebooted the host containing the VMs. So the proxmox-infrastructure is setup as cluster. So I connected pbs at Datacenter/cluster level. Where can I find out which host pbs connects to?

Will send you the versions when I know which host to check

Thanks and BR!

dcsapak · Jun 22, 2022

philipl said:
I rebooted the host containing the VMs. So the proxmox-infrastructure is setup as cluster. So I connected pbs at Datacenter/cluster level. Where can I find out which host pbs connects to?

with that i mean the host (hostname/ip) which you enter in your browser and you connect to.

File Restore not possible

New Member

Proxmox Retired Staff

New Member

Proxmox Retired Staff

New Member

Active Member

Proxmox Staff Member

Active Member

Proxmox Staff Member

Active Member

Proxmox Staff Member

Active Member

Proxmox Staff Member

Active Member

Proxmox Staff Member

Active Member

New Member

Proxmox Staff Member

New Member

Proxmox Staff Member