Quote from GTS:
I was going to ask why you clone instead of image - I do all my (backup) imaging to a network drive
As I think about your situation, what you do seems perfectly logical... assuming imaging to a HD is properly reliable.
Cloning is making an identical copy of your working drive. (If you had a 2nd HD in your machine you would have the option to clone to it.) The advantages of cloning: (1) much faster than imaging, (2) waaayy more reliable than imaging to optic media, (3) theoretically more reliable than imaging to another HD. If you presume the image to hard drive is always copied "perfectly", then they would be the same.
When your HD is "imaged", the software uses algorithmic conversions of the data to create one very large file.. which it plays back to "restore the image". If there is any corruption in that image file, the whole thing is lost. With cloning and there is a bit of a copy error (which there sometimes is... just as there is when imaging), only the affected function or program is damaged while the rest is OK.
While I've not cloned to a HD, I have to optic media... and I just hate it... lots of coasters. Lots of worry that I'll get "corrupted file" message when trying to restore even though I verified the file when the image is made. No such worries with cloning.... and did I say cloning was MUCH FASTER?
