Per-job aging out of backups?

[mark49808]

Maybe i'm missing something here, but if so its not obvious via the UI.

It appears to me that the way you tier data to object storage (capacity tier) is contained within the Scale-Out backup repository settings. You set the "Move backups to object storage as they age out of the operational restore window" option. However, that appears to be a setting that applies to the entire SOBR. If I have multiple jobs hitting the same SOBR (which seems like something everyone would have), and I want different retention per job (ie Job A should be on performance tier for 2 weeks, Job B should be on performance for 2 months, and Job C should never go to capacity tier) I don't see a way to do that.

Is there no configuration per job how long it should live on each tier?

Or do i have to do something that seems a bit "off" and create multiple SOBRs.....with potentially the same backing storage (just different paths)? I could then set each SOBR with different retention requirements. Does that even work? Or will that cause contention especially when considering XFS fast clone usage?

[veremin]

Scale-Out Backup Repository is seen as self-contained storage tiering system, so yes, it settings are applied to all jobs writing to it.

In order to achieve your goal you should indeed utilize multiple SOBRs.

Thanks!