Skip to main content

Mistakenly managed / renamed ATI 2010 archive (.tib) folders with Windows 7 File Explorer - What now?

Thread needs solution
Beginner
Posts: 5
Comments: 7

I have been using ATI Home 2010 regularly for over a decade (with great success), but find that my attempts to reorganize my collection of archives over the years (moving them to different folders in the file system with Windows File Explorer) has led to inconsistency with ATI's internal metadata directory.  I have not renamed any of the .tib filenames or sequences, but have simply organized some of them in different folders so they would be in one place. 

I now want to validate some of the ATI archives, but am having problems doing this because they are not in the file path where first created. 

Is there any way to rebuild the ATI metadata directory, specify an archive set by browsing with the Windows file explorer, or specify a standard file path to an archive set through a command line validation syntax?

Thanks for any help!

0 Users found this helpful
Beginner
Posts: 5
Comments: 7

How about an ATIH log viewer or command line tools for ATIH 2010?  Anyone???

Legend
Posts: 106
Comments: 26700

Sorry but ATI 2010 is now at least 11 years out of date / unsupported so any tools for this are never going to be provided by Acronis unless are already available.

If you have moved files / folders then this should have no impact on doing a recovery when using the Acronis bootable rescue media.  Only the Windows ATI application will be affected because of paths stored in its metadata database.

Beginner
Posts: 5
Comments: 7

Thanks for the reply, Steve.  I understand Acronis' preferences for annual software rebranding and recent move to software as a service, but the ATIH 2010 era perpetual licenses have worked just fine with my Win 7 operating systems.  Unfortunately I did not realize the significance of the internal metadata database when making changes to the folder structure of my windows archives.

Your point about how Acronis operates from its rescue media is enlightening.  Of course, you would not want to depend on an internal metadata database when it no longer exists or is buried deep in an Acronis archive. That's a handy tidbit, but I don't want to work off the rescue media for the project at hand as I have hundreds of granular .tib archives in various places in order to memorialize software development milestones that I've long ago forgotten.

I also discovered that Windows Explorer's context menu has an 'Archive' entry with Mount, Recover, and Validate among its right-click drop-downs.  This is convenient, but also apparently relies on Acronis' internal metadata database.

I did find a couple of forum posts about restoration of the internal database, but I'm not sure I want to risk the validity of my more recent primary disk images just in order to clean up my old mini-archives of project libraries from the 2010-2014 era.  Are there any better posts than these relevant to editing or re-syncing the internal database?

Thanks again for any information you can provide.

Legend
Posts: 106
Comments: 26700

The key issue with the internal database is that its use, structure and type has changed over time with different later versions, so any suggestions about rebuilding the database via deleting it and letting it rebuild may not be relevant to your 11 year old version of ATI.

The only suggestion that I would make here is to try another approach that may work for you.

If you have tasks shown in the ATI 2010 GUI for the relocated .tib files / folders, then take the option to Delete those tasks by just removing the task settings (leaving files intact).

Next, use the option to 'Add existing backups' to the GUI and select one of the most recent .tib files from its new location to be added back.  This should then allow you to validate that task and find any further files associated with the task, i.e. incremental files and repopulate the metadata database.

The above technique works fine with the later versions but is not something I have tried with any version as old as 2010 but I cannot think of any good reason that it should not be the same.