Solved

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

Posted on 2014-04-16
7
2,355 Views
Last Modified: 2014-11-12
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
0
Comment
Question by:IT_Crowd
7 Comments
 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 40005091
0
 
LVL 118
ID: 40005191
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
 
LVL 35

Assisted Solution

by:Mahesh
Mahesh earned 500 total points
ID: 40005204
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
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 13

Author Comment

by:IT_Crowd
ID: 40005229
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
 
LVL 35

Expert Comment

by:Mahesh
ID: 40005820
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
 
LVL 13

Accepted Solution

by:
IT_Crowd earned 0 total points
ID: 40007411
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
 
LVL 13

Author Closing Comment

by:IT_Crowd
ID: 40014373
Thank you for the help!
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

Suggested Solutions

#Citrix #Citrix Netscaler #HTTP Compression #Load Balance
OfficeMate Freezes on login or does not load after login credentials are input.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
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…

911 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