Best Practice for moving backups to a namespace while maintaining the existing backup job chains

[iceph03nix]

I'm looking at moving our backup targets around on PBS to make better use of namespace specific pruning jobs, and I'm curious before I make any changes if there's a best practice for moving the files so that when the backup jobs are retargetted they'll maintain the existing backup chains and retention can keep going on as expected.

I'm not sure if I'm overthinking this or not. I see I can move them in PBS, and I can change the target storage in the backup job, I'm just not sure if they'll recognize each other after the move.

 

[Johannes S]

The deduplication will continue to work in any case since it's cross-namespaces as long as you have them all on the same datastore. To get the backup snapshots to another namespace I would use a sync-job, for moving retention rules you will propably need to recreate the prune job on the new namespace.

For security reasons your ProxmoxVE host shouldn't do any retention, for keeping the backup jobs, just retarget them to the new backups targets