+1 from me
We also noticed this behaviour, we had large customers with thousands of users not being removed due to overlap with backup jobs and retention schedule.
We changed our retention schedules a few months back to 6 hours before the daily start of the jobs, that fixed it for us.
But a simple suggestion, just make the results of the retention tasks visible under History -> System, like in VBR where background maintenance tasks like rescans or inventory are visible under History.
The average sysadmin might now be completely unaware that this process is not running as it should and therefor might be paying more for (object) storage than they should.
We also noticed this behaviour, we had large customers with thousands of users not being removed due to overlap with backup jobs and retention schedule.
We changed our retention schedules a few months back to 6 hours before the daily start of the jobs, that fixed it for us.
But a simple suggestion, just make the results of the retention tasks visible under History -> System, like in VBR where background maintenance tasks like rescans or inventory are visible under History.
The average sysadmin might now be completely unaware that this process is not running as it should and therefor might be paying more for (object) storage than they should.
Statistics: Posted by AlexL — Jan 30, 2024 12:48 pm
