Direkt zum Inhalt

How to delete Images in True Image Database (i deleted them with Explorer)

Thread needs solution

I use True Image 2010. I deleted and renamed a few of my Images with the Windows Explorer. But now i see that these Images still exist in the True Image Database. How can i remove these Entries that only exist in the Database but not really on my Harddisk? The Manual doesnt say anything about that.

Is it possible to actualize (refresh) the Database)?

Sorry for my bad english ;)

0 Users found this helpful

I found a solution (workaround):

In Windows 7 in this path: C:\ProgramData\Acronis\TrueImageHome\Database i deleted the file "archives.xml". After starting True Image this file was generated again. And now all the images in the database were gone. The i go in True Image to Recovery and on browsed to all my Images manually and clicked on them.

This is not userfriendly. A function to refresh (scan the Harddisk for Images) the Database would be a better solution.

4942 Proper way to delete backup archives (*.tib) from your hard drive.
Particularly post #2 plus the post #5 for the 2010 version.
http://forum.acronis.com/forum/4942

I think you didn't understand what my problem was.

I _can_ delete the tib-files. The problem was that i delted them with the explorer BUT though in the Database from True Image they exist. This means they exist not really (because i deleted them), but the Database they are shown as existing.

A simple "Refresh"-Option to scan for EXISTING Tib-Files would be a solution.

btw NOW i know that i better delte the Images using True Image. But its easier to use Explorer.

I totally agree that a "refresh/scan existing .tib" files is needed.
The entire recovery catalog concept is great for business use where a catalog exists on a server seperate from what is being backed up. Furthermore business tend to have a much more dynamic/complex set of target locations for their backups and these vary day to day.

Conversely, In a home use situation where the catalog is local to the machine being backed up and source drive is pretty much a constant and the target drive (and folder) is pretty much a constant. In this situation the catalog is not an assest it actually a fragile representation of what "aught" to be the truth of what should exist. The archive.xml file is the fairly tale of what aught to be, but what actually exists on disk is the cold hard truth. I simply hate the fact the official solution is to ignore the cold hard truth and try and make the fairy tale system work. The catalog was introduced in 2009 and continues in 2010. It was a mistake. One doesn't even need it. If your system was to crash and you had to boot from cd and restore, the catalog wouldn't even exist. All you would have would be the .tib files and of course that would be enough.
In my opinion Acronis would be easier to use if either: A) the catalog (archive.xml) concept was simply turn-offable. One coudl have it if you didn't turn it off but one could turn it off. Acronis was totally functional in prior versions without it, it would be so again if we didn't have it. B) Give us both a command line and gui interface where we can have acronis go refresh its catalog based on the contents of what is in a target folder. that way the catalog can be made to match reality.

I just blow out the backup and log histories in ATI. That seems to work for me.

oracledba wrote:
In my opinion Acronis would be easier to use if either: A) the catalog (archive.xml) concept was simply turn-offable. One coudl have it if you didn't turn it off but one could turn it off. Acronis was totally functional in prior versions without it, it would be so again if we didn't have it.

I full agree for that. The prior Versions withot the catalog weres much better for ME. Sometimes i make an image from the the Recovery Manager from the Bootblock because its the fastest Solution. And then the image is not shown in the catalog. So the Catalog confuses me. AND its overloaded because i have different Images with the same Name (Iage 1, Image 2) in fifferent Folders (Windows XP, Windows Vista, Windows 7).

I really hate this solution with the catalog.

GoneToPlaid wrote:
I just blow out the backup and log histories in ATI. That seems to work for me.

How do you made this? You mean to delete the xml file?

To delete the backup archives from the database from within TI 2010 you need to do the following.

Click on the Recovery option.

From the list of disk backups (or file backups from the file backups tab) select the archive you wish to delete, right click and choose Remove.

Personally I'd expect to be able to do this from the Tasks and Logs area or even have a Archive maintenance tab.

This is no worse and no better than many photo catlogue programs. If you do file operations outside of the catalogue, the catalogue can become confused and inaccurate, reporting files that no longer exist or that have changed names. Some catalogues, expecting that such things can happen, handle this better than others. The ATI catalogue is a very primitive version of this and doesn't handle the possibility of outside operations at all. It is bascially a braindead database. It's one of the reasons that many of use that have have used ATI for years, stopped using so-called upgrades as of ATI 12/2009 when this all this database nonsense started.

What's kind of sad about ATI is that often it's problems are things that users work around manually in relativley straightforward, programmatic ways. Why, then Acronis couldn't have build these "workarounds" right into the program is at best a mystery and at worst a sorry comment on Acronis's respect for its users.

The old dos ways where better. tell the program what folder/s to look in and they make a list at the time of the request.

Thank you Peter - this worked a treat. I had a usb external drive that I trashed so I bacame increasingly annoyed when I could not get rid of the references in the Acronis user interface. Your post showing me where the "archives.xml" was situated saved the day. In a fit of pique I also deleted "mounted.xml" which seemed to do no harm.

Thank you Peter, worked for me when I deleted files through windows explorer. You are a champion. They should put a warning somewhere obvious - deleting from explorer is the default action for me. Didn't occur to me that it would case such trouble!

Thank you Peter, worked for me when I deleted files through windows explorer. You are a champion. They should put a warning somewhere obvious - deleting from explorer is the default action for me. Didn't occur to me that it would case such trouble!