Salta al contenuto principale

[Question] Acronis TI 2013: Removing Archives

Thread needs solution

How does one delete archives of partitions that no longer exist in the 'Archive selection' section of the Consolidation Wizard?

I have several single backups that link to 'paths' that no longer exist.

*Selecting them and click next yields the "need more than one backup to consolidate" error.

example:

Name: My_partitions_full_b2_s1_v1
Created: 11/21/2012 8:17:48 PM
Method: Full backup
Path: I:\Serena\My_partitions_full_b2_s1_v1.tib

That drive doesn't even exist anymore...I have 5 such backups that no longer link to the actual TIB file.

0 Users found this helpful

I think you can right click on the backup set name and select delete.

If they show up in the ATI interface, then click on the path and delete them. If not then navigate to them in Explorer and delete them. If ATI continues to show a backup set for the deleted backup, click on it and it will say can't find or some such thing and offer to ignore that backup-tell it to ignore.

This is what I mean: http://farm9.staticflickr.com/8391/8468343244_5f6d6ed3d6_b.jpg

The backups listed as E: and I: no longer exist, fact the I: drive is completely gone (reformatted into Y: drive). I want to know why the Consolidation Wizard is still registering them when the Backup and Restore portion of ATI clearly sees none of them.

---
Sorry for the late response...apparently 'notify' doesn't actually notify...

Because it doesn't know that you reformatted the drive. It could just drop them when it doesn't see them, but what if you brought the drive back (e.g., detached and later re-attached it?)

You can delete the backup entries as described above. Compared to prior version, ATI 2013 does a pretty good job keeping track of backups -- prior versions could orphan a backup with anyone fooling it.

In your case, you outsmarted it.

So...detach and re-attach is the suggested fix?

If so:
Well, I can't detach the I: drive as it's been reformatted to a different drive. And I don't have a spare drive.

The E: drive serves as the TMP/TEMP, User Profile, Browser Cache, and overall System Resource drive for my SSD "OS Drive". So detaching that would result in a BSoD or another unwanted error.

---
Really would be nice if Acronis put a 'Re-scan' option that would repopulate the Backup and Restore section and Consolidation section.

No, that's not the suggested action at all. I was just giving an example of why someone might want ATI to behave the way that it does. It's not right for all circumstances but there is a reason and a rescan (one that ignores all history) wouldn't always be a help.

You just want to tell ATI to delete those entries for backups you no longer have. See above for how to do this or refer to the manual. Basically if you try to make ATI use one of the files, it will tell you you can't find it and then you have an option to delete the entry.

Open ATI find the backup set for any one of the backups that no longer exists, click on the backup set name and tell me what you see.

Those entries for E: and I: show up ONLY in the Consolidation Wizard. They are not present anywhere else in the ATI program.

Those TIB files no longer exist, either.

This is precisely why I made this post. Clearly Acronis did not foresee people removing backups by directly deleting them from Windows Explorer or Reformatting the drive. And why would I even think to use ATI when those backups were no longer valid.

--It would be like me going to Add or Remove Programs and uninstalling software when I was going to do a fresh install of the operating system.

And if I try and consolidate them I, of course, get the "You need at least two versions to consolidate" error.

---
I suppose a reinstall of the program would remove the orphan entries, but what an annoyance.

As an alternative to reformatting the drive you can manually edit out with a text editor the orphan entries in the file:-

C:\ProgramData\Acronis\TrueImageHome\Database\archives.xml

Restart after editing and they will be gone!

Awkward and annoying way to have to do it I think but its the only way I've found to compensate for the lack of fore-thought exhibited in not simply allowing deletion of this annoying cr*p from within this program. Its been present in all versions of TI 2010 - 2013 atleast, so come on Acronis pull your finger out and solve this (and others) extremely annoying bugs/features/(lack of) design features!