I recently had a Windows XP SP3 system of mine die. I thought that I was in good shape as I regularly backup with Norton Ghost 14. I had periodically run a job to 'Backup my Computer" using a 'recovery point set' using Standard compression, but had not verified the recovery points. You can imagine my horror when I tried to restore my system after repairing the hardware, only to find that I was unable to perform a recovery of the 'Backup my Computer" It repeatedly would only tell me "The internal structure of the image file (CRC Check) is invalid, damaged, or unsupported - Error ED8000012".
I went through the forums in detail and the best that I could do was to restore only my 'Files and Folders' to a second set without compression. Then I went though the painful process of basically "rebuilding" my hard drive by loading Windows, installing all my applications, and then restoring the uncompressed data files. What a joy!
As part of this, I also bought a second new PC. While I was going through that rebuild, I also built a mirror system on it , even buying additional software licenses (as a backup, the failure made me a more than a bit afraid). Well, now that all is built, I tried my first backup. Again, I set up a job to 'Backup my Computer" using a 'recovery point set', only this time I set it to use no (None) compression as that seemed to be the issue previously, and I chose to Verify the recovery points. I reformatted my old USB-connected 1TB drive that had been my target before, and ran the backup job on my new PC.
Guess what! While wrapping up(I assume from the progress indicator bar) and performing the 'Verify', an Error ED8000012. Assured this was consistent with three attempts, and it was. Then I tried to run the same setup with a second internal hard drive as the target, with the same unsuccessful result. So, I tried it once without Verify to assure that was the issue; it ran successfully to completion. Except now I know that running without verify IS NOT A SUCCESS.
This issue seems terribly pervasive throughout the forum, and no one seems to have successfully found a true solution. I am certainly not going to go forward with a backup that cannot be verified. In fact, I hope that everyone learns that a Verify is a 'must' part of every backup. Have I overlooked a known fix to this problem? Is there a way for me to proceed, or must I invest in a competitive Backup/Restore software package?