Skip to main content

ATI 2014 Tasks

Thread needs solution

I have ATI 2014 Premium and for the most part it is working well for the two external disk rotation setup that I am using. With the help of GroverH and a few others, my configuration seems great, but old versions are not being deleted per the automatic cleanup rules.

My task configuration started off to be the same as what GroverH wrote to me in
http://forum.acronis.com/forum/45334
I probably started with "Store no more than" 3 version chains.

Within a few weeks, my disk filled up, so I deleted the oldest chains from within the ATI task that I have setup.

I have experimented with changing the Store no more than number and now have it at 1, but old chains are still not deleted. I've read in the forum where modifying an existing task can result in unexpected behavior by ATI. So my questions are in regards to tasks and existing backups.

Q1: Is changing the task value for "Store no more than" in an existing task, one of the quirks in ATI?

Q2: It seems that backup history is kept at the task level, not the disk level.

Q2a: If I create a new task, identical to the old task, but with a lower "Store no more than" value, will I lose the old backup history?

Q2b: If I will lose the old backup history for the old task, should I delete all old backup chains in the old task or reformat the drive before I use that drive in a new task?

Q3: Since there seems to be a problem with ATI not correctly handling task modifications, are the good folks at Acronis looking to fix this?

Note that I'm fine with reformatting my drive, but I would be happier if I can keep the old backup history when I create a new task on the existing drive. I'm also fine with keeping one version chain, assuming that the first is deleted after the second is created.

Thanks,
Dave

0 Users found this helpful

First, let's get a coupe of things out of the way. Some users are confused with "chains", and think they are backup files. A chain is a full and its partial backups (incremental or differential). Also, ATI will always try to do a new full backup before erasing any older chain.
Second, yes, changing the retention rules can lead to unexpected results. Worst case, ATI will get confused, or lose track of some older files. If you monitor the files manually, you can modify your retention rules, let ATI go through at least on new full cycle after the change, then control...
Compare the versions tracked by ATI with the files on the disk. Delete manually the backup files not tracked by ATI.
Otherwise, you could move the existing backup files to another directory on the same disk, then delete your task, then set up your new task. After the files are old enough, just delete the moved archives manually.

David,
In addition to the good advice offered by MVP Pat L, I will respond to each of your questions later. In the meantime, would you consider posting a screen capture of your most recent backup scheme plus a picture of the storage folder where the files are not being deleted.

In considering the available space on your disk, the sum of all tasks must be added together as it is the task which controls how many backup are retained but it is the disk which runs out of space--not the task.

What is the size of your storage disk which keeps filling up?

Q1: Editing is permitted by the program but most edits takes too long to a correction to occur within the process. A change does not occur immediately after the edit so if you are tight on space, you will probably fill up before the correct occurs.

Q2a: Yes, it is the user responsibiltiy to determine their space needs and set the configuration accordingly. If running multiple backup tasks, the space needed by each must be factored in. As indicted in all my posting on this topic, the user must factor in the method used by Acronis when a cleanup or deletion is due. The program will FIRST make the new full backup and after its creation, only then will it delete the old file. Thus, there is a short term need for additional storage space before the deletion occurs. The user must plan for the temp need to help prevent a disk full error. If that deletion only after new creation is a problem, you may have to manually (in advance) delete the backup scheduled for deletion prior to the programs creating the new replacement or utilize the help of helper program such as Chain2Gen.

If you have your backup scheme set to 1 full plus 6 incs (or 1 chain=7 files), and
store no more than 1 recent version chain,
then, the program will create the first chain (7 files) and also create the 2nd full before deleting the 7 files of chain 1. Space storage calculations needs to be made for the creation of the first 8 files.

Q2b: The loss of tasks is not a loss of history as the actual backup files still exist.
Any manual deletion or program deletion of actual backup files will be a loss of history.