Browse for Backup Doesn''t add the backup to the list
Using TI Home 11. I had a full backup on a removable drive that I copied to a internal hard drive to update incrementally because the external drive was full. I am unable to "Browse for Backup" to add the copy to the backup list. Why not?
I experienced something similar with ATI 2012 (Build 6131) using Win 7. I created an image on my internal HD and then copied it to my external HD. When I saw that the image file in the new location did not show in the Backup and Recovery tab's Backup List I tried to add it to the Backup List with Browse for Backup. I selected the file but when I clicked Add to Backup List it did not add it. Further, when I tried to Validate the copied file (with a right click on the file in Windows Explorer and selecting Validate from Archive) it seemed to validate the original version of the file on the internal drive as shown in the Backup List. Also, I could not add the copied file to the Backup List through Recovery. So, I could not recover from the copied file if I ever needed to. However, I was able to use the copied file from Recovery while booted to the TI Recovery CD. I guess I could recover that way, if need be. All of the above was also true when I tried the same thing by copying the image files to DVDs (I had the original image split for this purpose).
The only way I can get a copied image file to be listed in the Backup List for a different location (eg, my external HD) is to create it there in the first place (therefore it is an original and not a copy). But I'd like to be able to have copies of my image files in 2 locations to minimize the risk of loss due to things like lightning damage, disk failures, etc.
Here's my main question:
Short of creating images directly on multiple destinations (which takes more time), is there a way to get copies of my image files at different locations listed in the Backup List?
Solar,
You are witnessing a built-in issue with ATI. It tracks TIB files in its database, but the database update is tricky, and since ATI uses the database to show the tasks in the backup list, the behavior might be tricky. It can also lead to serious issues at recovery time, if the user moves/renames TIB files manually and loses track of the changes.
The right way to move a backup file is to use the move backup command from ATI. If you do this, though, the tracked TIB files of that task will be moved and the following backup will happen in the new destination. So it is not a copy.
Another way to get copies is to use the reserve copy option (in the advanced options). The issue is that reserved copies are only full backups, and are really 2 backups running consecutively, not a copy of a TIB file.
If you copy TIB files manually (not move them), it is not required to see them in your backup list for any meaningful ATi activity (restore, validate).
Make sure you either validate a copied file, or use copy software that verifies the copy. We have seen TIB files being corrupted by a simple copy (as reliable as an OS file copy is).
Thank you, Pat.
So, this is a known limitation of ATI.
I'm using the Version Scheme - so, the reserve copy function would not be an option for me (since you say it is Full Backup only). So, if I do a verified copy of the image files I would not need to validate the copies. Nor would I be able to do the validation of the copied files, anyway, (based on my experiences with ATI and what I understand you to be saying above). And I could do a recovery of the copied files only from a booted recovery CD (based on my experimentation). All of this is because ATI cannot add copied files to the Backup List (database).
Let me know if I misunderstood anything. Thank you!
Thank you, Pat.
So, this is a known limitation of ATI.
I'm using the Version Scheme - so, the reserve copy function would not be an option for me (since you say it is Full Backup only).
Correct. Reserve copies are always full copies
So, if I do a verified copy of the image files I would not need to validate the copies.
Correct. If you verify-copy a valid image, there is no way the copy cannot be valid.
Nor would I be able to do the validation of the copied files, anyway, (based on my experiences with ATI and what I understand you to be saying above).
You can validate the files without having them in the backup list. In Windows explorer, you can right click on a file, choose "archives > Validate"
And I could do a recovery of the copied files only from a booted recovery CD (based on my experimentation).
Using the recovery CD is the recommended way. At any rate, it has to work for you, because this is what you will need if your disk dies.
Thank you, Pat.
Regarding your comment:
"You can validate the files without having them in the backup list. In Windows explorer, you can right click on a file, choose "archives > Validate"
I stated above:
"Further, when I tried to Validate the copied file (with a right click on the file in Windows Explorer and selecting Validate from Archive) it seemed to validate the original version of the file on the internal drive as shown in the Backup List."
I tested that again (a moment ago). When I right clicked on a copied image file in Windows Explorer and selected validate it immediately started the validation operation. When it was done it gave me the "Validation Successful" message. However, the Backup List showed that it was validating the original image file and not the copied file - through the progress bar for that backup and through the resulting log file.
So, it does not appear to be validating my copied file. And I'm satisfied with just using the Verified Copy function instead of Validation for my copied image files.
Question: Is the "Copy /V" command in the Command window what you had in mind for a Verified Copy? Is that a good way to verify the copy?
The validation issue is weird and seems to be a bug. Did you try to change the name of the copied file and then do a validation?
Copy /v will not suffice. Some file comparison software or command would be better. http://answers.microsoft.com/en-us/windows/forum/windows_vista-files/do…
Another way to increase confidence is to mount the copied image. If it mounts, you have a high level of confidence you can extract the files from it.
Yes, I had tried renaming the copied files in 2 different tests and got the same result with the validation process in both tests - ie, ATI indicated it validated the original file and not the copied file. Maybe, ATI would indicate it that way on whatever the top listed, original backup was in the backup list?? I did not test for that. But either way it would not solve my problem.
I'll use your suggestions above to verify copied files.
Thanks!