2012 R2 Hyper-V Failover Cluster (VMs not failing over)

I have a two node 2012 R2 Hyper-V Failover Cluster. I've been able to migrate VMs between the two hosts successfully, but if I reboot one of the hosts, the VMs just power off instead of failing over to the second host.

I was under the impression that one of the hosts could do down and there would be no loss of service to the VMs.

What could be misconfigured?

-IT_Crowd
LVL 13
IT_CrowdAsked:
Who is Participating?
 
IT_CrowdConnect With a Mentor Author Commented:
Ok - so I think everything is resolved now. The original issue of failover not working I believe we can attribute to not enough RAM on the destination machine.

Regarding the Link Type not being set to Cluster. I needed to configure the Roles in Failover Cluster Manager to include all of our VMs. That will make them all Highly Available. Once they are HA, I can transfer any machine in the off state via Cluster instead of Network.

Thanks for the help!
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, if the Host fails due to a power outage, or uncontrolled shutdown e.g. pull the power out of the Node to Test.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
MaheshConnect With a Mentor ArchitectCommented:
In reality upto windows 2012 if you reboot one Hyper-V host, the VMs should go in saved state and then should come online on another node automatically
However if host restarted unexpectedly, the VMs will get restarted on another node

However with 2012 R2 some features get drastically changed  specially reboot of hyper-v node
http://windowsitpro.com/windows-server-2012-r2/failover-clustering

Can you check in every VM properties on node if "make this VM highly available" is selected and another node is selected as "Possible owner" in Cluster VM resource properties

Also ensure that VMs are placed on CSV volumes

Mahesh.
0
 
IT_CrowdAuthor Commented:
Ok - I will check on that as well. This is interesting as well. When I go to migrate some VMs, why do I see a transfer type of Network and others I see a transfer type of Cluster? All the VMs that I am trying to transfer are from the same host server, they are all going to the same destination server (apart of the same cluster), and they are all powered off. Any ideas? Could this be related?

Edit:  I did check to make sure the VMs are marked as High Availability, and some of them are set to HA, and others are grayed out with the box unchecked.
0
 
MaheshArchitectCommented:
Those VMs for which you are getting greyed out checkbox, they were placed out of CSV volume and causing they can't be make highly available

Can you check setting of each VM and check VHD \VHDX path where its locating ?

The path must be %systemroot%\ClusterStorage\Volume1\..........

Also CSV volume must be present on all clustered hyper-v nodes

If path is different, then the VM is not highly available

If path does not exists, then you don't have CSV volume enabled for attached shared storage

Mahesh.
0
 
IT_CrowdAuthor Commented:
Thank you for the help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.