Skip to main content

Back Up Drive becoming Full

Thread needs solution

Hello everyone.
I have the 2013 Version. I was checking by back-up files; I have one full back up and lots and lots of incremental files. The 1TB external hard drive is becoming full and I cannot see that my recent data has been backed up. Should I delete files to make room if so, which or should I wipe the back-up drive and start again?

Thanks for any advice, Thanks. Jim

0 Users found this helpful

http://forum.acronis.com/system/files/delete-backup-file.jpg
Informtion above about delete methods.

There really is no way of reducing the size of this particular backup as all files are needed in order to restore a recent file or recent backup.
So your choice is mostly to stop using the old task and recreate a new task but use the illustration below to set a reasonable limit on how many inc can be created before a new ful is perfomred.

The only deletes you can do this file is to delete a group of the newest files and keep the oldest. The chain must remain continuous in order to keeps its integrity. The is probably the oldest files you want to get rid of but unfortunately, it is the oldest that you must keep in order to be continuos from 1 to whatever.

Create a new task as per the below pointing the storage to a new or empty sub-folder to store the new future backups in.

http://forum.acronis.com/system/files/delete-backup-file.jpg

Figure 11-Inc: Example of custom/incremental backup method settings
If using incremental type backups (which is full + X Inc), the 11-Inc is my recommended method. Change the 6 or 4 to fit your available storage.
These automatic cleanup settings will provide for automatic deletion of the oldest backups after the "Store no more than X number of chains" quota has been reached.
In this example, deletion of oldest backup will occur immediately following creation of backup #29.

Allow space for 1 more full backup in addition to "Store no more than X number of chains" as the program will NOT delete the oldest full until its replacement has been successfully created.

In this example, one chain or one recent version chain =1 full plus 6 inc or 7 files per chain.
If keeping 4 recent version chains (4 chains of 7 each) retention would be 28 files. Deletion of oldest chain will occur after backup 29 (full).

Also understand the limitations/risk factor of incremental backups.
If one inc backups gets corrupt or accidentally deleted, all newer inc are worthless so avoid excessive number of incremental backups. Always maintain a full backup set which are current This explains why keeping a reasonable number of x "recent version chains" can be very important. Keeping a high number of incremental is a high risk factor to your backup data and should be avoided.
For a better understanding of the differences between Inc and Dif as it relates to the safety factor, review this link.
http://forum.acronis.com/forum/40810

When restoring an Incremental backup, select the specific Inc file to be restored and all preceding Incremental files plus the full backup base must be present and will be restored (multiple files required).