[SOLVED] Unable to restore PBS Backup on different PVE

D

dnut

Active Member
Proxmox Subscriber
May 6, 2016
23
7
43
42
Hi,
I'm not able to restore backup done on pve1 to pve2.
But I can correctly restore backup on pve1.
Storage is encrypted.

I proceeded as follows:
1. configured PBS storage on pve1, configuring encryption
2. did several backups
3. configured same PBS storage on pve2, importing encryption key (copying and pasting key) created on step 1
4. all backups are visible on the pve2

If I try to restore backup on pve2, process fails after being stuck for a while during the "download and verify backup index"
File restore seems to works from pve2, but, obviously, I can't test any single file

If I try to restore backup on pve1, restore works properly

I'm starting to doubt to be able to restore VMs after a Disaster (like a pve reinstallation on same or new hw).
Any suggestions?

Thank you

Failed Restore log
[CODE]Using encryption key from file descriptor.. Fingerprint: xxxxxx Using encryption key from file descriptor.. Fingerprint: xxxxxx Using encryption key from file descriptor.. Fingerprint: xxxxxx new volume ID is 'vm_store_01:vm-100120-disk-0' new volume ID is 'vm_store_01:vm-100120-disk-1' new volume ID is 'vm_store_01:vm-100120-disk-2' restore proxmox backup image: /usr/bin/pbs-restore --repository xxx@pbs@192.168.x.x:x vm/120/2024-01-13T17:00:00Z drive-efidisk0.img.fidx /dev/zvol/vm_store_01/vm-100120-disk-0 --verbose --format raw --keyfile /etc/pve/priv/storage/zav.enc --skip-zero connecting to repository 'x@pbs@192.168.x.x:x' open block backend for target '/dev/zvol/vm_store_01/vm-100120-disk-0' starting to restore snapshot 'vm/120/2024-01-13T17:00:00Z' download and verify backup index progress 100% (read 540672 bytes, zeroes = 0% (0 bytes), duration 0 sec) restore image complete (bytes=540672, duration=0.00s, speed=192.91MB/s) restore proxmox backup image: /usr/bin/pbs-restore --repository x@pbs@192.168.x.x:x vm/120/2024-01-13T17:00:00Z drive-scsi0.img.fidx /dev/zvol/vm_store_01/vm-100120-disk-1 --verbose --format raw --keyfile /etc/pve/priv/storage/zav.enc --skip-zero connecting to repository 'x@pbs@192.168.x.x:x' open block backend for target '/dev/zvol/vm_store_01/vm-100120-disk-1' starting to restore snapshot 'vm/120/2024-01-13T17:00:00Z' download and verify backup index progress 1% (read 2751463424 bytes, zeroes = 3% (88080384 bytes), duration 21 sec) restore failed: connection reset temporary volume 'vm_store_01:vm-100120-disk-0' sucessfuly removed temporary volume 'vm_store_01:vm-100120-disk-2' sucessfuly removed temporary volume 'vm_store_01:vm-100120-disk-1' sucessfuly removed error before or during data restore, some or all disks were not completely restored. VM 100120 state is NOT cleaned up. TASK ERROR: command '/usr/bin/pbs-restore --repository x@pbs@192.168.x.x:x vm/120/2024-01-13T17:00:00Z drive-scsi0.img.fidx /dev/zvol/vm_store_01/vm-100120-disk-1 --verbose --format raw --keyfile /etc/pve/priv/storage/zav.enc --skip-zero' failed: exit code 255[/CODE]

pve1
Code: 
proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve)
pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-9
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
pve-kernel-5.4: 6.4-19
pve-kernel-5.15.131-2-pve: 5.15.131-3
pve-kernel-5.15.39-3-pve: 5.15.39-3
pve-kernel-5.4.195-1-pve: 5.4.195-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: not correctly installed
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libqb0: 1.0.5-1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.2-1
proxmox-backup-file-restore: 3.1.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.3
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-2
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.5
pve-qemu-kvm: 8.1.2-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1

pve2
Code: 
proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve)
pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-6-pve-signed: 6.5.11-6
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2.16-18-pve: 6.2.16-18
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.2-1
proxmox-backup-file-restore: 3.1.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-2
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.5
pve-qemu-kvm: 8.1.2-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1

pbs
Code: 
proxmox-backup: 3.0.1 (running kernel: 6.5.11-7-pve)
proxmox-backup-server: 3.1.2-1 (running version: 3.1.2)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
pve-kernel-6.2.16-3-pve: 6.2.16-3
ifupdown2: 3.2.0-1+pmx7
libjs-extjs: 7.0.0-4
proxmox-backup-docs: 3.1.2-1
proxmox-backup-client: 3.1.2-1
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: not correctly installed
proxmox-widget-toolkit: 4.1.3
pve-xtermjs: 5.3.0-2
smartmontools: 7.3-pve1
zfsutils-linux: 2.2.2-pve1
 
Last edited:
Hey,

How did you have declared yours pbs on yours two nodes?
1 or 2 declarations in datastore view?
 
Solved!

1. removed the datastore on pve2
2. rebooted pve2
3. reconfigured the datastore on pve2

The restoration now works properly!

Who knows why...

Thank you for your help
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back