1

I've recently installed Windows Server 2012 to my test server to run Hyper-V test environment. I have bunch of old VMs which were created in Windows Server 2008 R2 Hyper-V which I didn't export in advance - I just have all VMs files created on old server. I was able to successfully import VMs with fixed VHD, but unable to do it with those which use differencing disks - import wizard unable to handle this. Most of my old VMs using differencing disks tied to one parent VHD.

Any advice on how to import them into Hyper-V 3.0?

Mikhail
  • 1,287
  • 3
  • 18
  • 35
  • I believe you should be able to merge the differencing disk into a new disk. Then use that new disk with the VM. – joeqwerty Mar 15 '13 at 10:59

3 Answers3

1

Don't think you can import differencing disks. For this disk type, differences are stored in the differencing disk, which starts with no data, and grows to store the unique data. The parent disk also will have lots of Input operations because it is the source or common denominator. This is not suitable for personal/assigned VDI VMs or server VMs because you cannot upgrade/resize the parent and inherit the changes; you have to delete the lot and start again. As a general best practice, always backup your VMs before making configuration changes. Please check out http://www.altaro.com/hyper-v-backup/ for effective Hyper-V backup.

Bernard Lai
  • 11
  • 2
0

Looks like everything works through Import out-of-box in Hyper-V 3.0, may issues was because I've moved folder with parent disks... If everything in its place Hyper-V is picking up location of parent from VM config... The only extra thing required is reassign new NIC i.e. connect your legacy VMs to virtual switch, which is handled by Import wizard and upgrade Integration tools.

Mikhail
  • 1,287
  • 3
  • 18
  • 35
0

we used this tool to accomplish the same task as you describe: http://backupchain.com/Hyper-V-Backup-Software.html

I don't think there's a way around it since the differencing disks appear to reference the old system. when you use a backup tool it reimports the VM into Hyper-V Manager

Claus
  • 1