Solved

Hyper-V VM Migrations that uses Multiple .VHD fi

Posted on 2014-02-14
4
529 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
  • 2
  • 2
4 Comments
 
LVL 56

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 56

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

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

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

Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
A procedure for exporting installed hotfix details of remote computers using powershell
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.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

932 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

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now