Manny
Peter2150
Hi Bill
WIth the exception of the continous incrementals which run all day, whenever I manually make an image, I test it by doing a full blown restore. Then I know it's good. I do image a lot. Never had a failure, except of course a couple if issues with beta versions, but that's what beta testing is all about.
Pete
So let me get this right. You have faith in it but still test it every time? Wasn't it Khrushchev who, among other things, said "Trust but verify" ?
Absolutely. Let us not forget we are working with computers, and software, and little hiccups happen. When I image I assume it's good based on experience, but what if a little gremlin slipped in, it can happen. This way, after imaging, and restoring, I know with certainty that the image is capable of restore, because it has done so, not because I assume it will.
One thing I've learned is that when you NEED to restore an image you are already under stress. You don't want the added stress about wondering if an image will restore.
Two now humorous examples.
1. I was beta testing KAV 6.0 and it was pretty straight forward. I was imaging the system every Friday evening. Turned it on Saturday, and noticed something funny so I rebooted. Had a trashed system. Restored my FDISR archive, and in minutes had a trashed system. No sweat, restore the image, and in short order it is now corrupted. Hmm, restored and image from two weeks back, and again, in short order the same corruption, same symptoms. When back to an even earlier image with same results. Really puzzling, and getting a bit scary. Went on line with a system, I didn't beta test on and it was fine. Light bulb time. Shut down my modem, did a restore, and it was fine. Turned off the KAV auto update and all was well. Turned out, KAV had released a corrupt driver to the beta server, so you'd restore an image, it would download the driver, and game over.
2. But even worse then that, I had been shown how you can in ShadowProtect use the partition table editor and zero out the table, deleting it.(Don't recommend playing with this). It worked. So one bright saturday morning, I had loaded up the Acronis Disk Director via Bartpe, and was playing with the same feature. Really bad idea. Got a BSOD. Tried rebooting Bartpe, and got another BSOD. No sweat just restore the system. Booting Winpe, got BSOD. Not a good feeling now. Finally I thought, I just take my trusty Windows XP CD and reinstall WIndows and then restore. When the WIndows CD generated a BSOD, a cold sweat developed. This is a really big Uh Oh. After 8 hours of grief, Bootit NG to the rescue. It was able to delete the corrupted partition table, and then I could restore.
The StorageCraft guys figured out there was a problem with the XP partition table subroutines. They could handle any partition table, no partition table, but if the partition table was corrupt, the just threw up there hands and quit, causing the blue screen.
Manny, I take nothing for granted.
Pete