Skip to main content

Recover from missing (very old) backup versions

Thread needs solution

True Image 2014, build 6673

The backup set is being backed up to one drive, but verification fails with a complaint about a tib file on a different drive. It seems the backup set jumps from one location to an older backup location.

Point is, some of those old files are no longer available. I cleaned them up in the usual way, deleting increments and saving a few full's, sparser and sparser working back a few years.

When I command it to verify, it says it can't find version 5, and I press Skip. Then it complains about 6, 8, 10, 11, etc. for a while. Then it starts over with 6, and works its way through again. Then it starts over again with 6, ... at some point I hit Cancel.

I can't find any way to tell it to just forget about them.

When it becomes necessary to do a restore, I expect to need only the Full and Increments up to the one I'm interested in; not backups from 3 years before that.

Every version seems more frustrating then the previous. A backup tool should be ROBUST and Fail-Safe! Why is there no apparent way to "scrub" and *recover* from missing/bad tib files rather than saying, "yea, it's bad, about 3 years back. sorry, can't do anything with any version whatsoever".

How do I bypass the unnecessary checking, and how do I edit the backup database of what it thinks is supposed to be present?

0 Users found this helpful

Greetings,
You may want to try renaming your archives.xml file... which will be rebuilt when you open the program.

Start by closing the program

Navigate to ◦/Documents and Settings/All Users/Application Data/Acronis/TrueImageHome/Database/archives.xml

Location may be slightly different depending on the version of ATIH or OS you are running.

You may need to enable display of hidden file and folders

Suggest you rename it to .old in case you need to revert.

In most cases when this is done, we suggest recreating tasks and repointing them back to the storage target

Before you restart the program, "get your ducks in a row". I'd put my back ups in one location in a logical order. The program does a good job finding its .tib files. Remember however that if a task that is expecting a certain number of sequential back ups and one or a set is missing, an existing task may not run, consolidate or work as expected. None of your back ups will be deleted or erased in doing this.

MVP GroverH is very good with consolidation, so is MVP Enchantech.