I don't think so. As a workaround you could create two namespaces on one node. One namespace where you write all your backups to and for example set pruning to only keep the last 5 backup snapshots (lets call it "short"). Then another namespace where you set the pruning to keep the last 100 backup snapshots (lets call it "long"). Then you could set up a local sync job to pull all backup snapshots from "short" to "long".
Another offsite PBS then could have a datastore and a sync job pulling only data from the "short" namespace, so only the last 5 backup snapshot would be synced.
As all data of a datastore gets deduplicated (even when in different namespaces) this shouldn't consume additional space.
Another offsite PBS then could have a datastore and a sync job pulling only data from the "short" namespace, so only the last 5 backup snapshot would be synced.
As all data of a datastore gets deduplicated (even when in different namespaces) this shouldn't consume additional space.
Last edited:
