Direkt zum Inhalt

CONSOLIDATE: Remove missing backup names from list

Thread needs solution

TI 2014 Build 6673

I have executed the consolidation process for those backups which need it. It was done via manual selection and process.

However, the list contains a number of backups that no longer exist anywhere. As such, I can't find a quick way to remove them from the list and therefore keep only those that are valid backup images.

Is there a way to go through and select (within TI 2014), then delete those that no longer exist? If so, where may it be found? If not, what is the registry key where the list is maintained? If no registry list, then what control table exists where the list is maintained, and can it be edited?

Thank you for any help on this matter.

0 Users found this helpful

Thank you for the link. However, I'm not sure my issue was clearly understood. I am aware of the process that is available via that method.

The real issue is using a different path. There are backups that are listed in a list that is accessible via the consolidation menu(s). That list includes backups that simply do not exist. They don't exist on backup media. They don't exist in File/Disk recovery options. They are not linked to any entry on the Backup and Recovery tab.

It is this list of backups - long gone for one reason or another - that I want to clean up; and reduce to actual backups present.

If there is another path, please let me know.

Thank you.

Apparently, no one has the answer. The approach that was first suggested clearly was not along the path that was requested.

This is probably because the internal database of ATI has been corrupted.
The file is located at c:\programdata\ACronis\Trueimagehome\Database\archives.xml
Shutdown Acronis
Stop the Acronis services using services.msc
Rename this file to archives.OLD
Restart the computer.

Thank you!

This approach certainly cleared up the phantom backups from the consolidation lists.

Sadly, it also cleared up those that were not phantoms.

I am banking that it will, as time progresses, rebuild the list of incremental backups now defined or perhaps I'll find a method that will rebuild the list for me.

I do believe there is a theory behind this. Specifically, Acronis does not have a "Tools & Utilities" to rebuild the archives.xml object. One that either: 1) Reads the list in the first place, and identifies legitimate backups and their children; or 2) One that clears the content, then using the existing Backup & Recovery list to rebuild the content.

Either utility appears to be a minimal impact, should the object become corrupt in the future.

Anyway, I think this approach will be sufficient at this time.

Thank you for your help!

What you should do is move manually the existing TIB files to another directory on the same drive (to avoid a long copy), then restart the tasks so that new files are created. When the moved files are old enough, delete them manually also.

Avoid consolidation as if it were the plague. Set up a new task which will do its own deletion after it reaches your predefined chains which is the "store X recent version chains".

GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains with automatic cleanup. The 6-4 is user choice.

https://forum.acronis.com/system/files/10-2inc-custom_keep64.jpg

Good idea. I think I shall follow it.

I've not delved to deeply into that, but I'll poke around and make sure I apply it where appropriate!

Thank you for the advice!

Any backup scheme which uses "elapsed dayis" or "disk size limit" is consolidation and merging of data which is why I use only the deletion of old backups to trim my storage as per my prior example. Also, no edits or changes to the tasks. Create the task and make no further changes.
Any change of schedule can be done from the main menu without using the "edit settings" task option.
You might find my link 2-A of interest. The ending part has a number of "GH" links which are examples of how to use the options.

I'm disappointed this doesn't appear to have been fixed, but I used the information above to go and edit the xml file to remove the entries that no longer exist. Works for me :)

Geoff wrote:
Works for me :)

Great!