[SOLVED] Tape Backup - Media-Set Empty

Jan 5, 2023
6
2
8
Hi all,

I recently setup a Proxmox backup server and had configured an LTO6 drive which worked for backup/restore from the datastore. Sadly the drive failed so I replaced it with LTO8 and found it couldn't read the old LTO6 tapes.

I ended up deleting the old media using
Code:
proxmox-tape media destroy BARCODE --force
The new LTO8 drive seems to be working OK with a new backup job completing successful:

Code:
2023-01-04T20:17:38-05:00: Starting tape backup job 'backup-store:media-pool:IBM-LTO8:monthly-job'
2023-01-04T20:17:38-05:00: update media online status
2023-01-04T20:17:39-05:00: media set uuid: 7b743e33-402d-4b4e-9b26-f110b85b1f6d
2023-01-04T20:17:39-05:00: found 25 groups
<snip>
2023-01-05T01:24:14-05:00: percentage done: 100.00% (25/25 groups)
2023-01-05T01:24:14-05:00: append media catalog
2023-01-05T01:24:14-05:00: TASK OK

The problem I have is the "Pool/Media-Set/Snapshot" content page shows only the date of the backup but no snapshots to restore.

Screenshot 2023-01-05 at 8.18.34 AM.png

Clicking on the restore icon shows an empty lis of snapshots:

Screenshot 2023-01-05 at 8.19.07 AM.png

I tried to export the current media thinking it was holding some lock on the media-set catalog but that didn't help.

Software versions:
Code:
proxmox-backup                2.3-1        running kernel: 5.15.83-1-pve
proxmox-backup-server         2.3.2-1      running version: 2.3.2
pve-kernel-5.15               7.3-1
pve-kernel-helper             7.3-1
pve-kernel-5.15.83-1-pve      5.15.83-1
pve-kernel-5.15.74-1-pve      5.15.74-1
ifupdown2                     3.1.0-1+pmx3
libjs-extjs                   7.0.0-1
proxmox-backup-docs           2.3.2-1
proxmox-backup-client         2.3.2-1
proxmox-mini-journalreader    1.2-1
proxmox-offline-mirror-helper unknown
proxmox-widget-toolkit        3.5.3
pve-xtermjs                   4.16.0-1
smartmontools                 7.2-pve3
zfsutils-linux                2.1.7-pve2

I'm at a loss and was hoping someone had some ideas on how to troubleshoot this. Thanks.
 
I tried a few additional steps like deleting the backup job, the media pool, and destroying the media via the command line. I then performed a catalog scan (which required a force switch) to reload the media-set. Still the same problem. What ended up fixing my problem was a downgrade of the software to 2.3.1-1.
 
Last edited:
Hi. I am just testing PBS and noticed this bug. Has this patch been commited to the no-subscription repo?
 
no, the package was not yet bumped so no new version is available yet
 
  • Like
Reactions: p4xel