Cannot find version 1 > I am alway make a full backup?

The deleted backups are gone so you cannot prevent the error messages for those but a change of backup schemes can prevent you getting those messages on future backups.

Stop using your currrent backup task and create a new task as illustrated below. These settings will enable the program to do its own automatic deletion of old backups so you retain a revolving of 3 or 4 full always. The deletion will be by the program so the messages will be avoided. Point the new task to a new storage folder or sub-folder.

Figure 11-Full: Example of custom/full backup method settingsIf using Full backups only, this is a recommended method. 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 #5.

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.

Thx for you quick response OK

I understand why I will follow you advice and great a new task..

Thanks Bob

I also do FULL backups and do my own cleanup of older backup files. This allows me to have several different backups in place with my own naming conventions and cleanup routines.
However, as above I fall foul of True Images system remembering all those files that no longer exist.
Is there any way I can get TI to simply forget about all previous entries of a backup and simply work with the file selected. For example, I can clear my backups list, browse for backup file, select one, then, given its a full backup I simply want to restore it. I don't need TI to make any other versioning decisions for me.

Hi ddk,
I share your pain. I too would prefer the non-use of the history tracking.
However, you can do things differently and make the procedures less miserable.

#1. Use the tracking to your advantage. Instead of manual deletion using Windows Explorer, do your manual deletions within the program deletes function and the program will do the deletions and know they are gone.

The below is the Acronis Backup Explorer view. It has many options, one of which is the DELETE opton for tib backups.
The user can select the most recent backup for deletion; or if some earlier backups are selected for deletion, then all the newer backups will be deleted as well. One good feature about this DELETE option, is that the program will tell you how many files willl be deleted and the user must confirm the DELETE as wanting to be done.

Note: this deletion of backup relates only to those created by this specific task. If you have other tib backup tasks with tib backup files to be deleted, you will need to open each task individually and delete that group using the same procedure as detailed in the prior paragraph. There is no one single DELETE OPTION that will delete all backup files as any deletion by the program is done at TASK LEVEL.

#2. or, The tracking is stored in a file named "archives.xml" found in the Acronis folder named "database."
This file can be edited with Notepad and depending upon how adept the user is at editing this kind of file, it is possible to edit out the backups which are to be manually deleted outside the program.

#3. Or, the archives.xml file can be deleted entirely which will DELETE ALL TASKS and delete all history. This deletion would be like a fresh install of the program.

#4. or, also utilize the custom backup scheme set to automatic cleanup (as shown above in prioor post) so the cleanup of old backups can be performed by the program automatically.

This link may also be of similar interest.
http://forum.acronis.com/forum/48295

Thanks GroverH, one of those was just what I needed. For me, manhandling the archive.xml is the way to go. I wrote a quick script that strips out all the sections pertaining to archive files that no longer exist.
If anyone else would like to pursue this option, I have included my script here. It's very quick and dirty but does the job. I have only looked at my setup, single full backups so it won't work for incrementals or split archives etc. I'm creating an EXE for mine but you could just as easily open up any MSOffice app, open the macro editor and paste it in there to run.
I'm sure it won't be popular with Acronis themselves so don't start complaining when TI can't find any of your archives, take a backup of archive.xml first (script keeps the old as archive.xmlx but this will be overwritten next run).

Very nice. Thank you. Others may have an interest as well.
Maybe I will try this "as is" on a ful with inc listing.
Right now, there is a couple user with this problem which involves the full with Inc.
Thanks for sharing.

Yes this is indeed a pain with Acronis 2014. Never had this issue with some prior versions I used to use.

I thought there was some way to actually restore the tib files regardless of the version not found message.
Not sure. Wrote Acronis and received no proper answer even after paying the $20. All they quote are the kb articles which did not help.

So I ask with great hope....
1. Is there an easier way to restore from any tib file you want regardless of the version or where it is stored-hard drive, USB, external hard drive?
2. If I deleted the archives.xml file would it then allow me to restore whatever I want?

Thank you
Peter

Peterc,
Your questions are too general to provide a specific respones.

1. If your question relates to restoring an incremental backup, then all PRIOR incrementals prior to the tib to be restored are required. The chain numbering needs to be sequential from beginning FULL up to the tib file you wish to restore. Each incrrmental has only a single part of the backup specific to that backup.
If you are restoring backup #10, then all prior 10 are required. if you are restroring #15, then all prior 15 are required. If you are restoring backup #100, then all 100 are required. If chain continuous from 1-75 but #76 has been deleted, then the file is restorable only uisng the parts 1-75 and any backup 77-100 is useless or non-restorable.

As long as the tib file is accessible in one single folder when booted via the TrueImage Recovery CD, it does not matter where or what the location is--as long as the file is accessible via the Recovery CD. However, all required tib files must be present in the same single storage folder.

2. The archives.xml file is a history file. It has no control over whether the file is restorable. Whether the xml file exists or not has no bearing on the restorability of a tib file.

3. Validation of a tib file can be performed to determiine whether restorable. The validation checks to see if all the pieces of the chain, backwards from your selected restore file, exist and non-corrupt. In general, Validation does not check backup content but check validity of the file structure.

GH25. Understanding differences between Incremental and Differential for Data Safety

Below is examples of how to set up your backup scheme so the deletion is done by the program and deletion by the individual not needed.

Below is how
GH11. Create Custom Full Backup Scheme.
Keep 4 versions (chains). The 4 is an example only with user choice for whatever number of chains to be retained best fits the individual needs..

GH12. Create Custom Incremental Backup Scheme.
Full +6 Inc, Keep 4 chains. The 6-4 is an example only with user choice for whatever number of chains to be retained best fits the individual needs.

GH13. Create Custom Differential Backup Scheme.
Full + 2 Diff, Keep 2 chains. The 2-2 is an example only with user choice for whatever number of chains to be retained best fits the individual needs.