Backups showing in PBS but not showing in PVE

[halatovic]

Hello everyone,

I have PVE server (v.8.0.4) using PBS storages on PBS1 server (v.3.0.2) and on PBS2 server (v.3.0.4). Backup jobs are configured and scheduled and are being stored to PBS2 while PBS1 is on different location and it syncs backups from PBS2. Everything regarding backups looks good and works fine. However, I am not able to get list of backups on PBS1 from PVE GUI or PVE CLI command pvesh get /nodes/localhost/storage/PBS1/content. I am able to get list of backups in PBS1 GUI.

Any ideas how to sort it out?

Best Regards

Haris

 

[Chris]

Hello everyone,

I have PVE server (v.8.0.4) using PBS storages on PBS1 server (v.3.0.2) and on PBS2 server (v.3.0.4). Backup jobs are configured and scheduled and are being stored to PBS2 while PBS1 is on different location and it syncs backups from PBS2. Everything regarding backups looks good and works fine. However, I am not able to get list of backups on PBS1 from PVE GUI or PVE CLI command pvesh get /nodes/localhost/storage/PBS1/content. I am able to get list of backups in PBS1 GUI.

Any ideas how to sort it out?

Best Regards

Haris

Hi,

did you setup the storage for PBS1 with a user/token which has the required permissions to get the contents? Also, do you use namespaces, maybe your storage is not connected to the correct backup namespace?

For more details of the required permissions, see https://pbs.proxmox.com/docs/user-management.html#access-control

 

[SkyZoThreaD]

Maybe you have multiple PBS connected...
When you look for backups on a vm, you have a dropdown selection menu in the top right corner to select the PBS you want.

 

[halatovic]

Maybe you have multiple PBS connected...
When you look for backups on a vm, you have a dropdown selection menu in the top right corner to select the PBS you want.

Hello SkyZoThreaD, that is not case. I have selected correct PBS in selection menu. Thnx

 

[halatovic]

Hi,

did you setup the storage for PBS1 with a user/token which has the required permissions to get the contents? Also, do you use namespaces, maybe your storage is not connected to the correct backup namespace?

For more details of the required permissions, see https://pbs.proxmox.com/docs/user-management.html#access-control

Hi Chris, I have double checked user definitions with proxmox-backup-manager acl list command and also I have checked content of /etc/proxmox-backup/acl.cfg files on both PBS servers and it looks good. I have checked content of /etc/pve/storage.cfg file on PVE server and it also looks good, definitions regarding users match to definitions on PBS servers. We do not use namespaces on PBS1 and PBS2.

However, I found little bit confusing that in PVE users token are not showing in GUI for either PBS servers but backups are showing for PBS2 but not showing for PBS1. Summary info is correctly shown for both storages:

PBS2 storage info on PVE:









PBS1 storage info on PVE:

 

[SkyZoThreaD]

Chris meant that the user (or token) you used to connect the "storage" PBS1 maybe does not have the permission to read the backups on PBS1.
In my case, in Datacenter -> Storage -> PBS1 -> edit :

The red_scribble@pbs is a user on the PBS realm.

And on the PBS, it has the role to read/write backups in datastore->yourdatastore->permissions :

 

[halatovic]

In my case it is almost identical:





However, when I grant aDatastoreAdmin role additionally like in case SkyZoThreaD shared above it worked for me as well:






Thanks a lot @SkyZoThreaD and @Chris

 

[SkyZoThreaD]

Yes! that's it DatastoreBackup can backup only
Maybe there is a middleground between Backup and Admin but i dont think this is That worrying.

You're welcome mate !

 

[JDC]

I had the identical issue, when moving from a test pbs to a production server...I ran sync jobs to move over the backups but could not see them from the pve cluster. DatabaseAdmin role made them all visible. Your posts helped me to solve it in 5 minutes. Thanks!
JDC

 

[gucki]

I have the same issue. To make sure it's not a permissions issue I gave my remote user full admin rights on the pbs:



The pves correcly show the pbs' datastore status:





However no backups are visible at all:



This is what the datastore (there's just one) looks like on the pbs:





My setup:
- pve cluster with 3 nodes running Virtual Environment 8.4.1
- pbs outside of this cluster running Backup Server 3.4.1

Thank you for your help

 

[Chris]

I have the same issue. To make sure it's not a permissions issue I gave my remote user full admin rights on the pbs:

View attachment 91277

The pves correcly show the pbs' datastore status:

View attachment 91285

View attachment 91278

However no backups are visible at all:

View attachment 91279

This is what the datastore (there's just one) looks like on the pbs:

View attachment 91280
View attachment 91281
View attachment 91284

My setup:
- pve cluster with 3 nodes running Virtual Environment 8.4.1
- pbs outside of this cluster running Backup Server 3.4.1

Thank you for your help

You have no VM or CT backups in the root namespace (host backups cannot be restore to PVE, therefore not shown), so there are no backups which can be restored to a PVE host. Please connect the PBS storage to the according namespace containing the virtual guest backups.

 

[Onslow]

However, when I grant aDatastoreAdmin role additionally like in case SkyZoThreaD shared above it worked for me as well:

Note that granting DatastoreAdmin role is NOT the most secure setup. If the PVE server is compromised, it can delete backups stored in the PBS server!

 

[Onslow]

Yes! that's it DatastoreBackup can backup only
Maybe there is a middleground between Backup and Admin

Yes, it is.
https://pbs.proxmox.com/docs/user-management.html#access-roles

DatastoreAdmin
Can do anything on existing datastores.

DatastoreAudit
Can view datastore metrics, settings and list content. But is not allowed toread the actual data.

DatastoreReader
Can inspect a datastore's or namespace's content and do restores.

DatastoreBackup
Can backup and restore owned backups.

 

[gucki]

You have no VM or CT backups in the root namespace (host backups cannot be restore to PVE, therefore not shown), so there are no backups which can be restored to a PVE host. Please connect the PBS storage to the according namespace containing the virtual guest backups.

Thank you, this solved my issue. However, I find it a bit counter-intuitive. I had assumed that granting access to the root namespace would display a tree of all available backups in PVE, similar to how it works in PBS.

I also have another question: why is it not possible to restore other backups directly in PVE? In my opinion, it should be possible to restore them to a raw volume or disk and then simply attach that to a manually created VM.

As a side note, I lowered the permissions from Admin to just DatastoreReader, and it still works as expected.

 

[Chris]

Thank you, this solved my issue. However, I find it a bit counter-intuitive. I had assumed that granting access to the root namespace would display a tree of all available backups in PVE, similar to how it works in PBS.

The PVE integration is limited to the scope of the namespace. Note that otherwise things might get out of hand rather easily, in particular VMID clashes. Also, your backups will end up in the configured namespace scope. The namespace feature was introduced to allow more fine grained organization of backups on the PBS side, e.g. to separate clusters using the same datastore.

I also have another question: why is it not possible to restore other backups directly in PVE? In my opinion, it should be possible to restore them to a raw volume or disk and then simply attach that to a manually created VM.

This is currently not implemented. Also, host backups are file level backups not block level backups, so a filesystem must be created on the volume first. You can already do this by manually creating your volume and filesystem, mount it on the PVE host and the use e.g. proxmox-backup-client restore <snapshot-name> <archive-anme>.pxar <path-to-your-mounted-filesystem> --ns <your-namespace> --repository=<your-repository>.