There are 9 replies, with the last one on August 14 2013 at 23:49:07 by sainokawara
Quote:
Please read the entire post before speculating. It is an example of why I would like to see a Verify option on Restore just like Backup.
I have done many successful Restores from a particular MR V5.2.6314 created BackupImage including three on Monday. Tuesday, I did not turn this system on. Wednesday, I booted MR V5.2.6354 under WinPE 4.0 and SUCCESSFULLY ran Restore from this BackupImage (without the Verify before restore option). Since it was to the identical device, I did the Verify. IT FAILED! Since I have been doing a Verify after a Restore, I have had ONE fail (for unknown reasons) but a subsequent Verify was successful. So, I tried again and established that they always failed at 22%.
I then reran the Restore (with the Verify before restore option) and got a message that the BackupImage was "corrupt" (Error 5) apparently during the actual Restore. So, I decided to start all over again after REBOOTING MR V5.2.6354 WinPE 4.0 and the Restore (with the Verify before restore option) ran SUCCESSFULL again. I ran Verify and it failed at 83%. So, I reran the Verify and it ran SUCCESSFULLY!
Before you start saying that my system is "marginal", I checked the statistics kept by the two HDDs involved and they indicate that NO I/O ERRORS have occurred on either device. Unlike most customers, I always create redundant BackupImages on different devices. With this and another HDD, I can isolate the failure to a particular HDD (if that is what it is). However, if I hadn't run a Verify after these Restores, I wouldn't have known that there was possible problem with the Restore! I REST MY CASE.
Quote:
Please read the entire post before speculating. It is an example of why I would like to see a Verify option on Restore just like Backup.
I have done many successful Restores from a particular MR V5.2.6314 created BackupImage including three on Monday. Tuesday, I did not turn this system on. Wednesday, I booted MR V5.2.6354 under WinPE 4.0 and SUCCESSFULLY ran Restore from this BackupImage (without the Verify before restore option). Since it was to the identical device, I did the Verify. IT FAILED! Since I have been doing a Verify after a Restore, I have had ONE fail (for unknown reasons) but a subsequent Verify was successful. So, I tried again and established that they always failed at 22%.
I then reran the Restore (with the Verify before restore option) and got a message that the BackupImage was "corrupt" (Error 5) apparently during the actual Restore. So, I decided to start all over again after REBOOTING MR V5.2.6354 WinPE 4.0 and the Restore (with the Verify before restore option) ran SUCCESSFULL again. I ran Verify and it failed at 83%. So, I reran the Verify and it ran SUCCESSFULLY!
Before you start saying that my system is "marginal", I checked the statistics kept by the two HDDs involved and they indicate that NO I/O ERRORS have occurred on either device. Unlike most customers, I always create redundant BackupImages on different devices. With this and another HDD, I can isolate the failure to a particular HDD (if that is what it is). However, if I hadn't run a Verify after these Restores, I wouldn't have known that there was possible problem with the Restore! I REST MY CASE.