Skip to main content

Failed to open backup

Thread needs solution

I have ATI 2013, backup to smb share, with automatic cleanup enabled. (Create a new full version after 21 incrementals, and store no more than 2 recent version chains.)

When the backup runs, I get a bunch of error messages, "Failed to open backup," that specify old files that no longer exist. I'm currently on backup_b9, and it's throwing error messages about being unable to find backup_b12, backup_b13, etc.

I tried deleting and recreating my backup job (as well as all the backups). I tried renaming my backup. I tried completely reinstalling ATI.

There must be a file, or a registry setting somewhere, that makes ATI look for these old backups. How can I completely clear it out and make ATI forget about the old backups?

Attachment Size
screen_shot_2015-09-12_at_5.17.55_pm.png 219.37 KB
0 Users found this helpful

Which version of Windows are you using? Win 7 was the last one which supported 2013,

I don't remember specific about 2013 but 2014 had a database folder as per GH55. Deleting this Database folder deleted the old history which is causing your problem You can see if GH55 will work for you. Caution. ALL of your backup tasks will need to be recreated.

GH55. Delete Database History Archives.xml.
GH55A. Acronis services

If you do not want the above, you could start over with a new task but with these changes.

When creating any new tasks:
1. Each task should have its own unique name. Don't reuse the same task name. No two tasks names alike.
2. I always recommend that each task has it own sub-folder so tib files from other tasks do not get mixed together.
You can use the same top folder but have a different sub-folder for each task.

Your backup scheme of full plus 21 incremental's; and store no more than 2 recent version chains, advises the program that your backup retention quota is 2 chains (22 files per chain) or 44 files to keep before automatic deletion begins Automatic deletion would occur after backup #45 (after Full B3) and oldest chain 1 is deleted.

I also find that making changes to a task does not work. Better to set it right the first time. If corrections needed, stop using the old task and create a new task with a new task name and new storage sub-folder.