PVE and namespaces with PBS

*Daedalus

New Member
Feb 5, 2024
13
2
3
I'm not sure if I'm just an idiot, or if what I'm trying to do just isn't possible for some reason, but here goes:

PVE cluster, connected to PBS, both latest versions as of today.
For the sake of not cluttering up the GUI, I have a single PBS connection to the root namespace.
In PVE I have configured a few pools based on VM/CT type - Critical, General, Templates, etc.
In PBS, I've configured several namespaces of the same name.
Currently, everything backs up to the root namespace, but I'd like to have each pool in its own namespace.*

Is there a reason why I can't do the obvious thing of backing up a given pool to a given namespace?
I know I could add a separate PBS connection for each namespace, but that seems... excessive.

Am I losing my mind? Is there something obvious I've missed here?

*Because at the moment the retention is handled on PVE, but I'd like PVE's PBS user to only have permission to write a backup, and not remove one, for a little extra security.
 
each storage represents a single namespace, so yes, you need to set up one for each
 
Is there any plan to support what I'm looking for, by any chance?

If the grouping that we can backup VMs with in PVE is pools, and the grouping for VMs in PBS is namespaces, then it seems logical to me to be able to backup a certain pool to a certain namespace.
 
that would require leaking storage internals into the backup config, which we try to avoid. setting up multiple storages works fine, and also allows to hand out different levels of access on the PVE side.