Skip to main content

Backup method problems

Thread needs solution
Beginner
Posts: 2
Comments: 2

  I have me method set to create a full version after every five incremental versions and to delete versions older than 11 days.

  And yet my 2TB backup drive keeps filling up as I have backups going all the way back to April 30. My PC hard drive has less than 460 GB on a  TB hard drive.

  Any idea what the problem is?

0 Users found this helpful
Legend
Posts: 100
Comments: 21992

#1

Wayne, how often are your backups being done?

When using the cleanup option of older than 11 days, the count does not begin until after your full plus 5 incrementals have all been created plus a new full backup made successfully.

So if you only backup once a week, it would take 7 weeks before the 11 days started counting up from 0.

Personally, I use the alternative cleanup option to 'Store no more than 2 recent version chains' which ensures that I am only storing a maximum of 2 x Full chains (2 x Full + 10 Incrementals) plus 1 more Full backup before the oldest chain (Full + 5 Incr) gets deleted.

When deleting any unwanted backup files that are filling up your backup drive, please only use the 'Clean up versions' tool in the main ATI GUI in the drop-down menu for your backup task, and not deleting the files in Explorer.

Beginner
Posts: 2
Comments: 2

#2

I'm backing up daily at around midnight and as far as I can tell I am creating a full version after every five incremental.

  I don't have the option "store no more than ( ) recent version chains," selected Should I?

Legend
Posts: 100
Comments: 21992

#3

Wayne, your opening post said: 

I have me method set to create a full version after every five incremental versions and to delete versions older than 11 days.

Try changing that to use 'Store no more than 2 recent version chains' instead of using 'Delete version chains older than 11 days'.

Beginner
Posts: 2
Comments: 2

#4

For whatever reason, old versions are still not being deleted.

  I have the scheme set as suggested, create a full version after every five incremental versions and store no more than 2 recent version chains.

  However, my drive have three full versions, and I think another is set to be created tonight, and it has versions going all the way back to July 5.

  The only problem is that unless I happen to go in and delete older versions the 2TB drive fills up and, of course, no new versions are created kind of defeating the point of regular backups.

Legend
Posts: 100
Comments: 21992

#5

Wayne, the only other suggestion at this point is to remove the schedule from the problem task then manually delete any unwanted backup version chains belonging to it, so that you have enough free space on your backup drive for new backups.

Next, create either a new backup task using a unique name that hasn't been used before, or else use the option to 'Clone settings' for the original task, but rename this before running it for the first time to ensure it has a unique name.  Check all the settings are as wanted then set that task to run per your original schedule.  This should remove any issues caused by the old task script or associated with its name.