How to access Hyper-V VMs on a Cluster Shared volume when Cluster is offline

Posted on 2015-01-08
Last Modified: 2015-01-14

I have a 2 node Win 2008 R2 Failover Cluster which I'm having difficulties getting online.
It's related to AD difficulties as far as I can tell.

For some reason I cannot Access the Cluster Shared Volume even though its listed as online in Failover Cluster Manager.

I really need to get one of the VMs stored on the CSV, and I'm wondering how this can be done?

For example: is it possible to take the CSV offline, remove it as a cluster shared volume, so that the "reserved" status the disk has in Disk Management will be gone? And then it can be accessed normally?

Or: what happens if I destroy the cluster (I'm in the process of moving the VMs to a New cluster in a New AD anyway).
Will this remove the reservation on the volume which now is the CSV, and let me Access the VMs on this volume from Hyper-V Manager? So I can continue to run them for a short while as I'm moving them one by one to their New home?

Any suggestions are welcome!
Question by:CSSGT
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
  • 3
  • 3
  • 3
LVL 24

Expert Comment

ID: 40539340
Some questions first:
- Is the CSV on some sort of SAN or NAS device?
- How do the cluster nodes connect to the CSV device: iSCSI, SAS, fibre?
- In the Failover Cluster Manager console, who is the Owner of the CSV set to and is this node online?
- Do you have a DC that is not on the failover cluster?
- Have you tried running the Cluster Validation wizard?

Author Comment

ID: 40539348
Hi, and thanks for helping!

- The CSV is on a SAN Device
- Fibre
- Yes, the node is online
- No, do not have a DC not on the cluster (anymore, used to have)
- No, haven't tried the validation wizard
LVL 24

Accepted Solution

VB ITS earned 250 total points
ID: 40539386
For some reason I cannot Access the Cluster Shared Volume even though its listed as online in Failover Cluster Manager.
Can you please advise the exact issue you are getting when you try to access the CSV?

Can you see the C:\ClusterStorage folder on the cluster nodes?
Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

LVL 39

Assisted Solution

by:Philip Elder
Philip Elder earned 250 total points
ID: 40539471
Make sure the DNS 0 and 1 on the node's management network point to active DNS servers.

Cluster will not come online if there is no DC available.

CSVs are in C:\ClusterStorage\VolumeX where the "X" would be the CSV volume number.

Author Closing Comment

ID: 40548838
Hi, sorry that I haven't been able to give an update sooner.

I had to work continously through the night and on Friday before I managed to solve the issue(s).

To summarize:

I managed to remove the CSV from the cluster, and Access the volume from Windows Explorer on one of the Hyper-V hosts.
This allowed med to copy the VHD-file for the VM I needed (the DC) to the local disk and create a new VM based on this file.

After bringing the DC online, when I tried to log on to the Hyper-V hosts, I got an error with the Security/trust relationship between this computer and the domain.

Then I had to log on with local admin, remove the server from the AD domain, reboot, re-join the domain and reboot.
Not a big problem, except that one of the 2 servers didn't have the standard password for the local admin account.
This was around 4 AM, didn't make me very happy :)

When I finally got around this problem and had gotten both Hyper-V hosts re-joined to the domain, with the DC running, I could get on with getting the Failover Cluster online.

Since I had to re-join the Hyper-V hosts to the domain, there was something wrong with the relationship between one of the hosts and the Cluster Name Resource. So the Cluster still wouldn't come online.

This could however be fixed by right clicking the Resource and selecting "Repair Active Directory Object".

So after a very unpleasent night and morning, I got the cluster back online.
So I can get the remaining VMs migrated over to my New Cluster.

Maybe it sounds very straightforward, but there were many little problems that had to be solved underways :)

Thanks for the contributions.

LVL 39

Expert Comment

by:Philip Elder
ID: 40548846
FYI: We always have a physical DC in our cluster settings. It is time authority on the network and provides an outside AD/DNS for cluster management and ongoing operations.

As far as the password situation look up: Crack the Cred episode 105.
Dana gives a simple step-by-step for resetting that password so long as the OS volume is not BitLocker encrypted.
LVL 24

Expert Comment

ID: 40548850
Don't worry CSSGT. We've all been there, fixing a cluster that won't come online until the wee hours of the morning.

For what it's worth I also do the same thing as Philip; have a physical DC that's not part of the cluster whatsoever.

Author Comment

ID: 40548858
Yes, always have a DC available not on the cluster :)

Problem was that this is a cluster that's part of an AD forest we're no longer a part of, after splitting up with another Company. But since you can't change the domain on the cluster to our new AD, it's still running until I get the last VMs out.

Not a preferable situation, as I was forcefully reminded of :)

LVL 39

Expert Comment

by:Philip Elder
ID: 40548895
As an alternative one can run a DC directly on the cluster node. That is, set up the VM on local storage within the local Hyper-V management. Fellow cluster and Hyper-V MVPs have indicated they do this in the absence of a physical DC on at least two nodes in the cluster.

For the cost of a Windows Server license and an HP MicroServer if an inexpensive 1U is not purchased it's worth it IMNSHO to have a physical DC. :)

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

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

Using the Hyper-V Manager requires administrator rights. This guide shows how to add shortcuts and Start Screen tiles for normal users to quickly connect to local virtual machines rather than using the recommended Remote Desktop connection.
Optimized for private cloud infrastructures and datacenters, Nano Server is minimalistic, yet super-efficient, OS for services such as Hyper-V and Hyper-V cluster. Learn how you can easily deploy Nano Server and unlock its power!
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …

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