ATIH 2011 Reinstall - All archive names lost
I recently had to uninstall and reinstall ATIH 2011, using build 6857. After doing so, all of my backups have lost their archive names. They are all now defaulted to names like "Disk Archive (9)", "Disk Archive (13)", etc. This is a mess!
How do I recover the archive names to the way they were before, when they showed the drive letters that were backed up?
Does the product always do this when you simply uninstall and reinstall it?
Thank you for your help.
When you start up ATI 2011, it scans for tibs and tries to match them up with what it previously had in it's database. This is one palce where ATI can get confused about which tibs exist, which don't, and which task the tibs beling to.
You can force ati to rescan/refresh. If that doesn't help, yo can try validating one of the tibs to see if they are still good [in which case move them aside but keep them] and check the actual filesnames of the tibs using windows explorer. It might just be the database that's confused. IF so, then delete the task and make a new one, preferably with the target directory empty.
My apologies for not checking the forum in quite awhile.
In response to your messages, I gave up in frustration and deleted all of my backups and recreated the backup jobs from scratch.
I've used ATIH for probably close to 10 years and continuously have problems with it, so this problem is just the latest. I'm a software engineer (30+ years) and I marvel at the flaky quality of this product. I tried all the options available on the user interface and couldn't figure out how to get my partition names back. I could only suspect that reinstalling the product wiped out its database and it cannot determine what its backups are from the actual backup files themselves. If that's true, then that's poor design.
Now I'm having a problem with it displaying (wildly) incorrect dates on the backups, which I have posted in a separate thread.
It pains me to admit that I keep pouring money into this product only to be continuously frustrated by its shortcomings/defects.
Scott: You mentioned "delete the task and make a new one, preferably with the target directory empty". What 'target directory' are you referring to?
Thanks everybody.
What Scott is suggesting is that you create a new backup task and direct the storage to an empty folder so the only backups to be stored inside the folder is from this single task.
I can see where your date problem could be a real problem. Any chance you have some redundant backups for comparison of byte count etc? Many of us use folder names plus file names to help identify what the backup is and what is included. While I have many different folders of backups archives, the folder itself only contains a few backup files.