Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Hyper-V R2 box that suffered a hard drive failure. Let me say, there was no redundancy in the box, but I was able to copy the folders for the 2 VMs that I needed to keep. Since I'm unable to boot and do a proper Export from Hyper-V, what are my options on getting these VMs working in a new installation? I know its not as simple as plopping them in a directory and having the server see them, and I can't import them without the .exp files.

share|improve this question
up vote 1 down vote accepted

The easiest thing to do is to copy the vhd disk to a directory on the new server.

Create a new VM in the Hyper-V manager and when it asks you whether you want to create a new disk or "use an existing virtual hard drive", choose the second option and select the VHD that you copied and start the VM.

It should work, I have recovered a couple of VM's this way.

share|improve this answer
I'll give that a shot. – DanBig Jan 22 '10 at 13:54
That did it. Sometimes its really easy to overlook the simple solutions. Thanks. – DanBig Jan 22 '10 at 14:19
This has long been resolved, but for posterity I have to add that if you were running from snapshots. You MUST, absolutely MUST keep your tongue straight, and do backups of every file before you start restoring them. If you mount from a base VHD, and not the current differencing snapshot VHD, then you will bork your VM. – Gomibushi Apr 16 '10 at 12:15

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.