Unable to restore VM from PBS

G

gtsatsis

Member
Nov 13, 2020
3
1
8
22
Hey there,

I recently reinstalled Proxmox, and I'm trying to restore the VMs from the Backup Server, but I'm having issues. All containers restored just fine, but VMs won't restore, and will give out an error like:

Code: 
TASK ERROR: command '/usr/bin/pbs-restore --repository anton2@pbs@10.0.1.218:Backups2 vm/108/2020-11-03T10:59:24Z drive-sata0.img.fidx /dev/pve/vm-120-disk-0 --verbose --skip-zero' failed: open3: exec of /usr/bin/pbs-restore --repository anton2@pbs@10.0.1.218:Backups2 vm/108/2020-11-03T10:59:24Z drive-sata0.img.fidx /dev/pve/vm-120-disk-0 --verbose --skip-zero failed: No such file or directory at /usr/share/perl5/PVE/Tools.pm line 441.

Would anyone have any idea as to what might be going on? How could I troubleshoot this more?

Cheers,
George
 
please post the output of pveversion -v
 
fabian said:
please post the output of pveversion -v
Click to expand...
Hey there, I'm so sorry for the extremely late reply, I had some issues IRL. Anyways, if you're still willing to help out, here's the output:

Code: 
root@pve:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.78-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.3-2
pve-kernel-helper: 6.3-2
pve-kernel-5.4.78-1-pve: 5.4.78-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-3
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.7.0-3
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.5-pve1
 
gtsatsis said:
Hey there, I'm so sorry for the extremely late reply, I had some issues IRL. Anyways, if you're still willing to help out, here's the output:

Code: 
root@pve:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.78-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.3-2
pve-kernel-helper: 6.3-2
pve-kernel-5.4.78-1-pve: 5.4.78-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-3
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.7.0-3
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.5-pve1
Click to expand...
So uh.. Turns out, as I just realized, I was incredibly out of date. Updating seems to have fixed the issue!
 
  • Like
Reactions: t.lamprecht
You must log in or register to reply here.
Top Bottom