Feature Request: Split retention of backup files Into a separate Job

[JGM2023]

Hello,

I would like to raise the following feature request: Split retention of backup files Into a separate Job.

Reasons: Currently It's very hard to monitor If retention Is working correctly, Especially with Immutable storage. When you have 100's of Backup Jobs this becomes a nightmare task. It's very hard for us to check If we have expired data/orphaned data on our Immutable storage. We see differences In growth from our local storage vs Immutable, We also often have never ending growth on some jobs which does not seem normal behaviour.

If this was split Into a similar console as a SQL Job for example then I feel It would be a lot easier to trace. It would run 24/7, You could monitor each backup Job and It's retention In one single place. There also should be an option to pause delete operations If required (Nice to have In the event of an outage If you want to ensure your environment Is focusing all resources on backing up for a short period rather than using task slots for deletes)

This Is referring mostly to Immutable storage retention.

[Gostev]

Hello, you should not need to worry about monitoring if retention policy is working correctly, honestly that's just too much babysitting for a backup product. Few people will want or have time to micromanage at this level, so I don't see us investing into building this functionality. Especially since it means touching the proven retention processing code that has been around forever and thus received much bugfix, in particular for various corner cases and negative scenarios already.

If there's lack of trust on your side, then let's rather make sure you have enough confidence that it does work correctly so you don't have too worry about this in the future. If you suspect it does not, please open a support case and have them investigate the particular "suspicious" backup files to confirm everything is working as intended (or if not, we will fix it).

Thank you