Solved

Hyper-V VM Migrations that uses Multiple .VHD fi

Posted on 2014-02-14
4
546 Views
Last Modified: 2014-11-12
Hi,
I am preparing to move a Virtual Machine. This VM is configured with Hyper-V and uses a total of 3 separate .vhd files for its drive structure. I am moving this to a different host which has more resources for increasing performance.

I have moved Virtual Machines before but they all used a single .vhd file.

How should I prepare to migrate a more complex Virtual Machine with multiple .vhd files.

Thanks for your suggestions.
0
Comment
Question by:carloc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 39860493
Nothing special. It still works the same way.
0
 

Author Comment

by:carloc
ID: 39860540
Is the process to create a new VM with the existing vhd file for the System OS, then add the extra drives and add the drive letter mapping.
0
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 39860755
That is not how VMs are normally moved, but that would technically work. Because it is a new VM, you will have HAL and network issues on first boot.

The more common method to move a VM is dependent on environment and connectivity. Export/import is the most flexible option insofar as you can export to a USB drive or whatever, and import from there. This preserves all of your VM settings including NIC MAC, etc so you avoid some hairy problems. The export process would export all attached VHD(x)s automatically so again, whether you have one or ten makes no difference.

Similarly live migration would do the same, as would shared-nothing live migrations. Storage management and attachment is all handled by the VMM service.

But even with a full manual move of VHDs and creating a new VM, the process is the same whether you have one virtual drive or ten. If you have one, you create a new VM and specifiy the VHD (and perhaps have to reset ACLs so the VMM service can attach the drive.) And if you have ten? Same thing. You still have to copy the VHDs and you still have to attach them and you still have to potentially reset ACLs. There is nothing "special" about the first VHD from a VM standpoint. From the guest standpoint it is obviously a bootable drive and has system data, but that is purely within the guest. The VMM doesn't care.
0
 

Author Closing Comment

by:carloc
ID: 40018272
Thanks for your help. I was eventually able to complete the move. Great Advice.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
Resolve DNS query failed errors for Exchange
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question