So what is the point of "testing" a recovery point?

I'm aware that a common theme is to check/test your image even though you all say it's a very "scarey" process, i.e. not sure what is going to happen. I have restored some individual files from my external HD with Ghost 10 successfully. Recently, I was having a problem with an unknown device (I have since fixed the issue) and attempted to just restore the drivers in System32 and it really messed up the desktop. Admittedly that was probably just me doing something I shouldn't have. There may have been more problems but I didn't wait around to find out. Fortunately a reboot in safe mode and restore and all was back to normal. Perhaps a 100% image restore would go without a hitch but if your PC is working fine, why run the risk with a test restore if the test can cause potential problems?

 

I believe you need to do a test restore to make sure your imaging software works properly. It's better to find out early on if it works, then to find out when you really depend on it to work (this is one of the reasons I switched from ATI to Paragon).

When I do a fresh install, I image it and then test to make sure it restores properly. I repeat this a few times when setting up a system to make sure it works properly and I keep all the images until I know I can depend on my imaging software.

 

Because a backup is no good if it can't be restored.

I can see your point though - there really is no way to properly test a image restore. You could test it with a bare install to be sure you don't lose any data, or you can test in a VM. However most people will install it on a pc they use, and won't have a 2nd pc to test on (which wouldn't mean much for the original pc anyway). So in this case you have to -

1. trust the software works, or
2. backup all your data, and be prepared to reinstall if the restore screws up

Both of these are frankly less than optimal!

 

I concur with testing at least crtical ones as peter stated.If your not going to test at least make sure the archives are good and If needed, knock on wood through salt over the shoulder and prey to the computer gods.

 

You need to run a "test restore" on a different spare hard drive, then swap out the drives. This way you will boot up with the "restored" drive. That's the safe way to test your recovery plan without risking your "main" hard drive.

From my personal experience I know that all backup/restore software can cause problems. If you do a test restore and it fails to boot, it will give you an opportunity to troubleshoot the problem. That's the main reason to test your recovery plan, to see if it will work when you really need it and if it doesn't you can learn how to fix it in a "controlled" environment.

On my system, I've disable "windows system restore" and rely on my imaging software to restore me. For me when restoring an image back to the same hard drive/same partition has proven reliable everytime. It's when you restore to different hard drives/partitions that problems show up.