Solved

Hyper-V, SCVMM 2008 and Failover clustering volume GUIDS

Posted on 2009-06-30
5
887 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
[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
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

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

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

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
Suggested Courses

631 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