Quick note - When I posted this originally I guess I didn't make it clear enough that I was only interested in Windows virtualization e.g. HyperV and thus was looking for Experts who were familiar and had administered such setups so the response I got was not relevant to me. I would appreciate this time around only people with HyperV experience responding. Thanks.
I am familiar with administering Windows networks that have physical servers and have experience in troubleshooting server crashes in these 'real' environments and carrying out recovery in a variety of situations. As far as virtual machines with virtual hard drives - again in the Windows environment - I have some questions:
1) The bad - what types of thing can cause a crash on a virtual machine/virtual hard drive that would never be the case on a physical machine/hard drive?
2) The good - what types of things that would crash a physical machine/ hard drive would never crash a virtual machine?
3) The bad - what new recovery techniques might be required for virtual machines/virtual hard drives that were never required on physical machines/hard drives?
4) The good - what recovery techniques can I throw into the legacy memory pool with virtual machines/virtual hard drives that I needed for physical servers/hard drives?
A couple of qualifiers.
a) I know my questions are open-ended so I don't need an exhaustive list for each answer - top 3, top 5 type of thing is enough - not worried about totally obscure rare situations - good links to clear info is as good as an answer
b) My overall sense is that with virtual machines and virtual hard drives as opposed to their real brothers and sisters is that the rule of thumb is 1) less problems 2) easier to recover from when they do happen. Is that general idea correct?