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.
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.