Solved

Hyper-V, SCVMM 2008 and Failover clustering volume GUIDS

Posted on 2009-06-30
5
868 Views
Last Modified: 2013-11-08
I have about 25 VMs on Hyper-v in a 4 node Windows 2008 Failover cluster.  I created the first 6 or so VMs before I learned about using volume GUIDs instead of drive letters.  How can I successfully change the existing VMs using drive letters to use volume GUIDs.  I learned the hard way that you simply cannot go into Failover Clustering and change the drive letter of the shared storage object since when the VM restarts, it no longer finds itself and getting it back is a difficult process.

I hear there is a possibility of manually editing the XML for the VM, but I also understand this is not a supported option and I am not sure it would work anyway.
0
Comment
Question by:vppinc
  • 2
  • 2
5 Comments
 
LVL 15

Expert Comment

by:plimpias
ID: 24767168
your best bet to take the safe side is to migrate them to another host that is not in the cluster. Fix the GUID on your cluster and migrate it back.
0
 
LVL 15

Expert Comment

by:plimpias
ID: 24773777
Also to add to this, delete all your snaps. shutdown the VM and let it finish the merge. Backup the VMM files. Delete the drive, create a new GUID an move it all back to it and add a new virtual machine and reconfigure your VM settings.
0
 

Author Comment

by:vppinc
ID: 24773864
What a pain.  Not worth it.  I will leave these at drive letter for now until Microsoft comes up with a quick way to change it.
0
 
LVL 3

Expert Comment

by:mdmiddle
ID: 24798021
This is what I have done in the past...
- Shut down the VM.  
- Using Hyper-V Manager, Export it to a new location
- From a command prompt, use Mountvol to list the GUID associated with the drive letter that is being used.  Copy the GIUD path.
- Remove the drive letter from the volume using Disk Management
- In Hyper-V Manager, start the Import process
- Use the GUID copied above as the target location
**TIP:  If you add an extra backslash to the end of the GUID path you can click Browse and browse the directory (it works elsewhere too).
- Complete the import process and start the VM.

HTH!
0
 

Accepted Solution

by:
vppinc earned 0 total points
ID: 25198904
Rumors that R2 handles this.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Join & Write a Comment

When working with Microsoft SCVMM (System Center Virtual Machine Manager) in a Hyper-V virtualization environment, we have run across scenarios in which the failed migration of a VM from one host to another may leave the VM in a failed state. Specif…
I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

759 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

22 Experts available now in Live!

Get 1:1 Help Now