[SOLVED] proxmox ve file restore

[juniper]

Hi,

i have an error if i try file restore functionality:


obviously i have backup on pbs and i have tried on all backupped vm i have.

Some suggestion?

 

[juniper]

on PBS appear



But on cluster interface i have: proxmox-file-restore failed: Error: given image 'drive-virtio0.img.fidx' not found (500)

 

[juniper]

on /var/log/proxmox-backup/file-restore

[2021-04-28T16:51:04+02:00] PBS file restore VM log
[init-shim] beginning user space setup
[init-shim] reached daemon start after 0.46s
[2021-04-28T14:51:05Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-virtio0.img.fi'): found partition '/dev/vda2' (2, 53683945472B)
[2021-04-28T14:51:05Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-virtio0.img.fi'): found partition '/dev/vda1' (1, 1048576B)
[2021-04-28T14:51:05Z ERROR proxmox_backup::server::rest] GET /api2/json/list?path=ZHJpdmUtdmlydGlvMC5pbWcuZmlkeA%3D%3D: 400 Bad Request: [client 0.0.0.0:807] given image 'drive-virtio0.img.fidx' not found

 

[dietmar]

Ah, this is an issue with virtio drives, which should be fixed by
'proxmox-backup-file-restore 1.1.5-2' currently in pvetest. We found
that issue a bit too late for the release, unfortunately.

See:
https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=606828cc65feb380c0f9536fe7ca277ea1dc20c1

 

[christian.g]

Ah, this is an issue with virtio drives, which should be fixed by
'proxmox-backup-file-restore 1.1.5-2' currently in pvetest. We found
that issue a bit too late for the release, unfortunately.

See:
https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=606828cc65feb380c0f9536fe7ca277ea1dc20c1

I stumbled across that issue right now too. Thanks for the update and i appreciate the link to the commit.

 

[t.lamprecht]

FYI, the respective update is now also out on the pve-no-subscription repository.

 

[christian.g]

Awesome, thank you.

I already have an improvement suggestion:
Select multiple files at once (multiselect) for download

 

[juniper]

Solved with proxmox-backup-file-restore update

 

[Peter123]

We set up a new PBS and now have the same problem.


Has the patch now been incorporated into the repo or does it still have to be installed manually?

 

[t.lamprecht]

We set up a new PBS and now have the same problem.

Has the patch now been incorporated into the repo or does it still have to be installed manually?

Yes, since almost a year, what version do you use? proxmox-backup-manager versions --verbose

 

[Peter123]

Yes, since almost a year, what version do you use? proxmox-backup-manager versions --verbose

root@pbs:~# proxmox-backup-manager versions --verbose
proxmox-backup 2.1-1 running kernel: 5.13.19-6-pve
proxmox-backup-server 2.1.6-1 running version: 2.1.6
pve-kernel-helper 7.2-1
pve-kernel-5.13 7.1-9
pve-kernel-5.13.19-6-pve 5.13.19-15
pve-kernel-5.13.19-5-pve 5.13.19-13
pve-kernel-5.13.19-1-pve 5.13.19-3
ifupdown2 3.1.0-1+pmx3
libjs-extjs 7.0.0-1
proxmox-backup-docs 2.1.6-1
proxmox-backup-client 2.1.6-1
proxmox-mini-journalreader 1.2-1
proxmox-widget-toolkit 3.4-9
pve-xtermjs 4.16.0-1
smartmontools 7.2-pve3
zfsutils-linux 2.1.4-pve1

 

[fabian]

the tpmstate is not file-restorable anyway, there is no filesystem on there it's just the raw state of the software TPM.

 

[Peter123]

the tpmstate is not file-restorable anyway, there is no filesystem on there it's just the raw state of the software TPM.

Yes, we knew this was the case.

However, the error message appears after the first call of "file restore", i.e. before a folder was selected. This is irritating.

Then, where files can be restored from, they can actually be restored.

 

[fabian]

yeah, the tpmstate should probably be filtered out there