Automatic Cleanup stopped working

Peter, sorry but not enough information to best advise you on this issue.

What backup scheme are you using?  Full, Incremental, Differential?

If Incremental or Differential, how many such files before making a new Full backup?

How often are you running this task, i.e. daily, weekly, monthly?

Just to set this in context, automatic cleanup of 'Delete versions older than 9 days' will only be applied after a new Full backup has been created.

So, if you make a weekly backup with 5 incremental backups before a new full one, then the 9 days would not count until the new full was created on week 7 which would then be day 0.

Full backup daily.

ok, thanks for confirming the schedule.

Day 1 - full backup - being kept via do not delete option selected.

Day 2 - full backup will be deleted 9 days after next backup is created on Day 3.

Day 3 - full backup will be deleted 9 days after the backup created on Day 4.

In essence you need space on your backup drive to be able to store at least 11 full backup files (including keeping the initial full backup).

What is the average size of your full backup files, and the size of your backup drive?

Average backup size is 142GB, backup drive 1.8TB.  Currently, despite my settings, there are 12 backups on the drive, and it shows 244GB space remaining.

Peter, have any of the backup settings been changed since this task was setup as this has been known to cause similar issues?

Otherwise, you would need to review the backup logs (ti_demon & backup_worker) to see if they offer any clues to what is happening?  The logs are found at C:\ProgramData\Acronis\TrueImageHome\Logs in folders by the same names.

On a personal note, I never use the option to 'Delete versions older than...' as I prefer to have better control by using the alternative option to 'Store no more than X versions' which has always worked as expected for me. 

Peter, was this working before? Were any errors encountered during the past ten or so days? TIBX or TIB files?

I think you should expect to have 11 backups, so you need room on the drive for 12. My understanding is that for a backup to be older than 9 days, it would be 10 days old (based on the daily update). So there would be the first backup, then 10 sequential backups. Backup 2 is 9 days older than backup 11 so it would still be there for another day.

I could be wrong... I don't use this feature. Like Steve, I always cleanup based on number of versions, not days.

I just switched it to number of versions.  Thanks for the suggestion.  I'll revert if that doesn't work.

It didn't work.  I wonder if the simplest fix might be uninstall/reinstall?  If so, can you provide an instruction link for that?

Thanks.

Peter, I don't think the reinstall would be useful.

Are you able to use manual cleanup to get rid of the older versions so you will only have left what you want. Then, you could see if that may help clean up the database and get it back on track.

If that fails, probably best to just create a new backup task. Since you are only doing daily full backups, the new task should be fine and you could manually delete older backups on the older task (to keep space available) until the new task up the the right number of backups.

I tried the manual cleanup, and it didn't work, so I'll set up a new task and try that.

Thanks.

Deleted my old backup tasks, set for "Store no more than 1+ 9 recent versions", left a total of 10 backups on the remote hard drive, and last night it did an 11th backup.  The hard drive will run out of room tonight on the 12th backup.

Any other ideas?

Thanks.

Peter, my only suggestion would be to remove the schedule for this backup task, then create a new backup task (with a unique task name) along with using the ATI 2020 task 'Clean up versions' tool to make some more space on your destination drive if needed, then schedule the new task to run in place of the original task (but with further clean up versions actions to stop the new task from running out of space to store files as it continues).