[SOLVED] Backups synced on Remotes not shown in PVE

[d1nuc0m]

Hi all,
I have a cluster with several PVE 8.x nodes and two PBS 3.x nodes, and somehow backups made on PBS1 and synced to PBS2 are not shown in the PVE node (although they're visible in PBS2 web UI and the disk usage is shown correctly in PVE summary).

I've read Backups showing in PBS but not showing in PVE, but still can't find a solution:

• I'm making my backups on PBS1/datastore01 with my PVE admin user, I can restore/delete/etc them. PBS1 is added in Datacenter/Storage using root@pam
• There is a sync job from PBS1/datastore01 to PBS2/datastore02 using a service user with DatastoreAdmin and DatastoreReader roles. I also tried using root@pam (same result)
• PBS2 is added in Datacenter/Storage, I tried using root@pam, an admin service user and a user with DatastoreAdmin role - always with the same result
• From PVE nodes I can't view backups on PBS2 (after selecting it in the dropdown in the Backup tab of a VM)

Does anyone have a suggestion? Thanks

 

[tcabernoch]

This is a wild shot ... did you setup Namespaces?
When you start syncing backups between systems, it can be a good idea to use Namespaces. I recommend it.
And misconfigured Namespaces would totally hide your backups but let you see disk was full.
But you probly didn't setup Namespaces ... people don't do that till they really need it. Mostly.

 

[Chris]

Hi all,
I have a cluster with several PVE 8.x nodes and two PBS 3.x nodes, and somehow backups made on PBS1 and synced to PBS2 are not shown in the PVE node (although they're visible in PBS2 web UI and the disk usage is shown correctly in PVE summary).

I've read Backups showing in PBS but not showing in PVE, but still can't find a solution:

• I'm making my backups on PBS1/datastore01 with my PVE admin user, I can restore/delete/etc them. PBS1 is added in Datacenter/Storage using root@pam
• There is a sync job from PBS1/datastore01 to PBS2/datastore02 using a service user with DatastoreAdmin and DatastoreReader roles. I also tried using root@pam (same result)
• PBS2 is added in Datacenter/Storage, I tried using root@pam, an admin service user and a user with DatastoreAdmin role - always with the same result
• From PVE nodes I can't view backups on PBS2 (after selecting it in the dropdown in the Backup tab of a VM)

Does anyone have a suggestion? Thanks

Hi,
are you using api tokens for accessing the datastores? Please note that you have to set permissions on the api token itself, as these are strictly separated from the permissions of the user.

 

[d1nuc0m]

Hi,
are you using api tokens for accessing the datastores?

No, I am not using API tokens at all (yet)

This is a wild shot ... did you setup Namespaces?

That was it... I had added both PBS servers to PVE with the root Namespace.
Instead now:

1. I added only PBS1 to PVE
2. created the backups on PBS1
3. Synced them from PBS1 to PBS2. On PBS2, this created in datastore02 the namespace my-proxmox-cluster under Root
4. Now I added PBS2 to PVE, specifying my-proxmox-cluster as Namespace instead of Root
5. Done, I can now see backups on PBS2 from PVE

 

[tcabernoch]

Cool. Namespaces are critical for sync scenarios. Mostly, you find that out after you mix your VM populations, and it can get weird.

If you have two PVE environments, consider giving them each their own vmid range.

Click on the cluster Datacenter root node. > Click Options in the middle column. > Adjust the Next Free VMID Range.

 

[d1nuc0m]

If you have two PVE environments, consider giving them each their own vmid range.

Thank you, like if I have a development and a production PVEs I should give them different VMIDs even if they are backing up to different namespaces? Like Root/my-proxmox-production-cluster and Root/my-proxmox-development-cluster?

 

[tcabernoch]

Well, think of it this way. If they all had their own VMIDs, unique across both systems, then there would be no technical need for different namespaces. You could mix the VM populations and still easily tell which was which. (There are many non-technical, logistical reasons to use Namespaces.)

By default tho, the first VM in a cluster is vmid/100. If you dump all the backups for two VMs with that name into the same directory, its gonna work, but its gonna look reeeeeally weird and confuse any humans looking at it. If you make your second cluster/standalone system default to vmid/200, then you will never have a conflict. At all. Ever.

 

[d1nuc0m]

Thanks a lot, I think I'll have to learn about namespaces

 

[simrsta]

This is a wild shot ... did you setup Namespaces?
When you start syncing backups between systems, it can be a good idea to use Namespaces. I recommend it.
And misconfigured Namespaces would totally hide your backups but let you see disk was full.
But you probly didn't setup Namespaces ... people don't do that till they really need it. Mostly.

how to setup namespace???

I have successfully done a remote sync from PBS 1 to PBS 2

but when pve proxmox I want to add pbs 2 so that at any time we can restore from pbs 2, the backup file is not found?

 

[omgs]

how to setup namespace???

I have successfully done a remote sync from PBS 1 to PBS 2

but when pve proxmox I want to add pbs 2 so that at any time we can restore from pbs 2, the backup file is not found?

I guess that's because the storage defined in pve points to a different namespace where the backup is stored.

 

[tcabernoch]

Yes, the problem described above sounds like the namespace setting needs configured in the Storage mount settings in PVE.
The setting is not editable after you create the mount, so just make a new one and fill out the Namespace bit.


I have one sever mounted twice in order to backup and restore from two different namespaces. This is normal stuff. Give it a shot.