Skip to main content

Backups no longer deleting old backups.

Thread needs solution

I not if this just being a problem with 2018 version I am now using but when I backup and I used to 1 full and 4 incrementals it used to delete the the prior backups so that was fine for me to just have the most recent backups and delete the rest. 

That method no longer works I tried stating the backing as full and incremental with 5 backups and nether scheme works so what am I missing to get this working again? Thanks

 

0 Users found this helpful

Techman, this is working fine for me, but can be affected if you have changed the backup scheme settings for your task, i.e. to increase from keeping just 4 incrementals to keeping 5.  This change can cause the count of incrementals to be reset for the version chain, so you could end up have up to 9 incrementals before the automatic cleanup will run!

The screen shot below shows the settings that I use which are working fine for me.

2018-01-15 12_27_07 Backup Scheme.png

Steve, I'm in the same boat for different reasons (don't ask). My incremental is set to keep 31 versions, and I think it's started counting over. It's up to version 35.

Do you know of any way to force it to start a new incremental chain?

Jerry, the only real way of forcing a new version chain would be to use the 'Clone settings' option for the task, edit the task name to make it slightly different to the original name, then remove the original task settings and run the new task.  This will leave your original version chain intact and start a new full backup for the new task version chain (assuming that you have sufficient free space to hold both).

If space is an issue, then you can manually delete the old task files after removing the settings for that task.