Version chains not deleting

This is the method to use when deleting old files.

GH5. How to delete backup files using Acronis Backup 'Explorer'

As for the cause, who knows but changing the specs when the task is in use has been reported to cause the chain to produce unexpected results. The log file should explain. It appears the incrementals part was added on 29th or 30th after the task was in use for full only.

I would delete all but the most recent full using the method described above.
start with the March 26 and delele the oldest files until you get to the April 27. Do not delete the April 27 full.

Hopefully, this willl get the program back on track. If it still continues not to auto delete, ultimately, stop using the this task and create a whole new task.

https://forum.acronis.com/forum/56872

Did you change your backup task after first creating it? Screenshots show that full backups occurred 03/26,29,30, 04/17,27.

This does not follow your current task rules. You should delete this task a create a new task. Here is a link to how to create a custom incremental backup task:

https://forum.acronis.com/system/files/custom_inc_keep64.jpg

GroverH wrote:

This is the method to use when deleting old files.
GH5. How to delete backup files using Acronis Backup 'Explorer'

GroverH,

If the Acronis method of deleting is not used will it become disconnected from an internal record and thus fail with later backups?

I ask because I just looked at a "Failed to backup" task and it's looking for full backup number b3, but the current full backup is b12.

I wonder if this is causing other issues with failures to backup and whether this is the reason a new task is the best, and only(?), way to cause a reset in Acronis?

NOTE: This is full backups, not differential/incremental ones.

If the Acronis method of deleting is not used will it become disconnected from an internal record and thus fail with later backups?

Yes. My experience has been that any deletion not done within the program causes the history file to be mismatched and the backup will fail looking for the missing files.

The program seems to correctly track the deletions done WITHIN the program and continue with correct numbering and without any error message.
Incrementals:--- Keeping in mind that deletion of incrmentals can only be done by deleting the newest or most recently created first. Any first deletion of older incrmental will cause the task to fail as its continuous chain has been broken because missing link is missing data which was backed up.
Differential---- Any diff can be deleted (within the program) and remains will be restorable.
Full--------------Each full is standalone so any full can be deleted (within the program) and remains will be restorable.

In my testing, the backup scheme that works for me has been the custom ones with automatic cleanup and "store no more than X" as per the example below. The version scheme involves consolidation and and I choose not to use any scheme which involves consolidation. The cleanup options of elapsed days or size quota is not part of my recommendtions.

My suggestion for you would be to stop using the version chain task. Create a new custom task as per my example with automatic cleanup (store X) so deletions are done by the program. Any deletions done by the user should be done from within the program.

GH11. Create Custom Full Backup Scheme.Keep 4 versions (chains).
GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains.
GH13. Create Custom Differential Backup Scheme. 2 Diff, Keep 2 chains.
GH14. Custom Differential Backup Scheme . 6 Diff, Keep 4 chains. & folder

Ditto Grovers comments. Any manual deletion on the users part not using the available delete functions built into the TI app will result in the applications backup database, which stores all information about what backups have been created and where those backups are located, will corrupt the database log file and result in any number of problems including failed backups.

Thanks, this probably explains, more than most, many of my recent issues.

My normal routine used to be full backups to one folder then move them out into a grandfather, father, son cycle of folders.

If removal of the backup, instead of copying, is causing the issues I'll have to alter my routines.

Obviously I never had this with the previous version of TIH 2010 for the last five five years of successful work.

Yep, we heard that from many 2010 users: big differences between that version and the following versions. Everything is organized around tasks and then there is this database that attempts to keep track of backups that have been done but can be get off sync easily with manual TIB archives operations done outside of the ATI UI.

Obviously I should have read the new manual and discovered all this, assuming it is all covered in the manual.

I've solved my problems by reverting to 2010. I can't afford the time to diagnose all the issues I'm having with 2014 Premium. Maybe in a few months I'll look at it all again, or wait for a new service pack to test out.