Scheduled validation fails
I'm using ATI Home 2010 build 7160 with XP Pro SP3. I've scheduled a full backup to a separate partition and it is created as expected. However, I want to run a scheduled validation on the backup image some time after the backup task is finished and the validation task invariably fails. I can perform an unscheduled validation that generally passes (unless there's really a problem with the backup), but scheduled validation on the very same image fails. The error code in the log (on the failure line and "show details" link is 0x00040002, but there is no info on that code.
The one exception is that when the backup task is first created and run I can then create the scheduled validation task and it works. This isn't simply because the task runs immediately (unscheduled) even though it is set to run at a later time. The scheduled validation that runs later on the newly created image passes. It's only after the image is overwritten by the next scheduled backup that the scheduled validation task begins to fail.
I looked at the renaming and moving issue (topic #3886) and tried browsing to find the backup; that did not help.
I tried copying the newly created image to a different disk and then copying it back to the original location after running the scheduled backup task to create a new image that failed scheduled validation. The copy of the copy passed scheduled validation.
Ultimately I want to copy images (full scheduled backups with non-changing file names) made on machine 'A' to machine 'B' and validate them on machine 'B' to make sure they have not been corrupted during copying, but I can't even get that far staying on machine 'A'.
Any assistance would be appreciated. Thank you!
Yes, manual validation passes (assuming the image isn't actually corrupt, and it rarely is.)
Good. What I meant is the following: with 2011 it is possible to set the validation to happen automatically right after the backup completes. Is it possible with your version? When you do that, does the validation complete?
ATI Home 2010 does not (as far as I can tell) provide the option to validate on completion the way 2011 does. In 2010 the next best thing is to schedule validation to occur once the backup task has had ample time to complete. The validation task requires a backup image file in order to be defined to begin with, so the backup task has to be run the first time before a validation task can be created. Once that is done the validation passes until a subsequent backup image is created (by the original backup task, with new full image overwriting the original and an identical image file name.) After that, scheduled validation fails but manually it passes.
I am doing a test installation of 2011 so I can describe the exact behavior of that version to you; will advise. Thank you for your assistance, Pat!
If you test 2011, you should first do a full backup, uninstall 2010, reboot and then install 2011.
Did that and ran the ATI cleaner tool as well. However, it's beside the point.
The 2011 version includes the option to validate an image upon creation (why wouldn't you?) and that passes. You can also schedule periodic validation so the closest approximation to 2010 function would be to turn off validation after imaging and then schedule validation for some later time. I will test that just for the record.
The deal-killer for me is that 2011 does not appear to permit scheduled validation of images created on alternate machines and then copied to the local machine. I can validate them manually in 2011, but I could do that in 2010 as well; it was only trying to run scheduled validations that got strange. As far as I can tell, in 2011 the scheduled validation function is accessible only as an extension of image creation, which appears to be limited to partitions on the local machine. I've not looked into imaging a mapped drive but I do not want to introduce the uncertainties of backing up over a network.
I guess what I would like to know is whether the problem I'm experiencing with 2010 is really a bug that others are seeing also or if this is somehow an issue unique to my own systems, perhaps an unholy interaction with another program. In 2011 it's not an issue because the functionality (which I need) has been removed.
Thanks for your insights.