none
Windows server 2012 hyper-V - disable the failover cluster RRS feed

  • Question

  • Hello everyone,

    Is there any way to disable the failover cluster on the hyper V windows server 2012?

    I want to disable it in a virtual machine or if possible in a general way in the entire hyper-v cluster

    Thanks in advanced

    Manuel


    Warm regards MeVs

    Monday, October 21, 2019 7:09 PM

All replies

  • Hi Manuel,

    The whole purpose of a Hyper-V failover cluster is to be able to run a virtual machine on any node in the cluster, providing high availability.

    You cannot "disable" live migration, but it is possible to modify the possible owners for the VMs.

    1. Open Failover Cluster Manager.

    2. Under Roles select a VM.

    3. In the bottom pane expand the Virtual Machine resource in the Resources tab.

    4. Right click on the VM configuration and select Properties.

    5. In the Properties dialog select the Advanced Properties tab.

    6. Deselect all nodes except the current node then click OK.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, October 21, 2019 7:16 PM
  • You'll have to disable the cluster services from the Host server(s). The cluster configuration is set up on the hosts and guest VMs don't have direct access to this. https://docs.microsoft.com/en-us/powershell/module/failoverclusters/stop-cluster?view=win10-ps stop-cluster is the powershell command you'll need to use to stop services for all hosts in the cluster and stop the clustered applications.
    Monday, October 21, 2019 7:18 PM
  • Hi,

    Thank you for posting in forum!

    Before we moved on, please help me clarify your question clearly.

    >>I want to disable it in a virtual machine or if possible in a general way in the entire hyper-v cluster

    Do you want to disable VM failover to another node or you want to disable failover cluster feature from our VM.

    1. If you don’t want the vm to failover to other nodes,  please take the following steps:

    1). Open Failover Cluster Manager.

    2). Under Roles select a VM.

    3). In the bottom pane expand the Virtual Machine resource in the Resources tab.

    4). Right click on the VM configuration and select Properties.

    5). In the Properties dialog select the Advanced Properties tab.

    6). Deselect all nodes except the current node then click OK.

    2.If you want to disable failover cluster feature from our VM, you can use one of the following methods:

    1).Use the powershell cmdlet stop-cluster on the hyper-v host.

    Reference:https://docs.microsoft.com/en-us/powershell/module/failoverclusters/stop-cluster?view=win10-ps

    2).On the hyper-v host, open services snap-in, stop failover cluster service.

    Hope this can help you.

    Best Regards,

    Lily Yang


    针对Windows 2008/2008R2的扩展支持将于2020年结束,之后微软将不再为其提供安全更新。点击此处 或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》,把握良机完成云迁移并实现业务现代化。

    Tuesday, October 22, 2019 9:18 AM
  • Hi,

    Just checking in to see if the information provided was helpful. 

    Please let us know if you would like further assistance.

    Best Regards,

    Lily

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Friday, October 25, 2019 8:57 AM
  • Hi,

    Was your issue resolved? 

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Lily

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Monday, October 28, 2019 1:52 AM
  • Hi LiLy

    In response to your inquiry,
    "Do you want to disable VM failover to another node or you want to disable failover cluster feature from our VM?".

    Yes, I want to disable VM failover to another node.

    I followed steps you post here  but they did not work.

    The scenary was my host get damage and no matter if I have VMs running on it, I just want they do not move to another hosts

    I keep in mind, this quote:
    "The whole purpose of a Hyper-V failover cluster is to be able to run a virtual machine on any node in the cluster, providing high availability."

    Does it possible to do what I tell in hyper v server 2012?


    Warm regards MeVs


    • Edited by MeVs Thursday, October 31, 2019 8:26 PM
    Thursday, October 31, 2019 5:39 PM
  • hi Lily,

    My issue was not resolved


    Warm regards MeVs

    Thursday, October 31, 2019 5:46 PM
  • After applying the settings shown below on a host, I only have one virtual machine on it.

    The host was sent to restart and while the host was "shutting down", the virtual machine that was on, was passed to another blade but turned off.

    When the host "started", the virtual machine that shut down, returned to the host that restarted but "turned on"

    I check the following configuration, maybe this is the expected behavior, isn't it?

    I was waiting for the host to shut down without moving the virtual one due to the configuration made.

    Here is the configuration screenshoot we did:

     


    Warm regards MeVs




    • Edited by MeVs Thursday, October 31, 2019 9:21 PM
    Thursday, October 31, 2019 8:50 PM
  • You are looking at the wrong settings, there are Possible Owners and Preferred Owners.

    You need to uncheck the Possible Owners, to do so:

    1. Select a virtual machine in the Failover Cluster Manager.

    2. At the bottom of the Failover Cluster Manager, you will see a Summary and Resources tab, click on the Resources tab.

    3. Right-click the Virtual Machine resource (found at the bottom) and select Properties.

    4. Go to the Advanced Policies tab and uncheck all cluster nodes that you don't want the VM to be able to migrate to.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 31, 2019 9:09 PM
  • Could you indicate if the option is located in the same place in both HyperV server 2012 and Hyper V server 2016?

    My query is only to validate, because the servers I have are Hyper Server 2012 and I think you passed me hyper server 2016 images.

    I will appreciate your response

    Warm regards MeVs

    Thursday, October 31, 2019 10:22 PM
  • It is in exactly the same place on Hyper-V 2012.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 31, 2019 10:27 PM
  • With this configuration, the MV will remain in the node (the example in the image), even if the node is shut down, restarted or ultimately damaged?

    Something similar happened to me, but the team moved to another node in off mode and once the node was recovered the MV moved to its origin in on mode.

    Regards,
    Julio
    Thursday, October 31, 2019 11:38 PM
  • When configuring Possible Owners, it will not be possible for the virtual machine to move to an excluded cluster node by any method without removing the restriction.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 31, 2019 11:45 PM
  • You are looking at the wrong settings, there are Possible Owners and Preferred Owners.

    You need to uncheck the Possible Owners, to do so:

    1. Select a virtual machine in the Failover Cluster Manager.

    2. At the bottom of the Failover Cluster Manager, you will see a Summary and Resources tab, click on the Resources tab.

    3. Right-click the Virtual Machine resource (found at the bottom) and select Properties.

    4. Go to the Advanced Policies tab and uncheck all cluster nodes that you don't want the VM to be able to migrate to.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thank you very much, I will tell the hyper V specialist to check this point shortly and look for the correct configuration


    Warm regards MeVs

    Saturday, November 2, 2019 3:24 PM
  • Thanks Leon
    So it may be happening in my environment, as I explained at the time of configuring in possible owners where I only leave a single node as a possible owner the rest deactivates them, at the moment that the node restarts or shuts down, they move to another node and that It should not happen, the strange thing is that they move in off mode and once the proprietary node starts they move to their origin in on mode.

    I was reading and I found this

    "For Possible Owners, absolutely, positively not come online on a node that is not a possible owner.  If no possible owner nodes are up, then the groups will still failover to a node that’s not a possible owner, but it will not come online."

    I am a little confused. Can someone help me?

    Regards,
    Julio

    Saturday, November 2, 2019 5:07 PM
  • Well if the node shuts down / restarts it's a different story of course and in this case the resources would fail over but not go online, failover clusters are made this way.

    Maybe you should in this case think of simply using standalone hosts instead.



    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, November 2, 2019 8:52 PM
  • Hi,

    If you want the host to shut down without moving the virtual one, the vm doesn’t need to be clustered.

    You can remove the vm from failover cluster.

    Hope this can help you. Please let us know if you would like further assistance.

    Best Regards,

    Lily Yang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 4, 2019 6:33 AM
  • The hyper-v specialist is also posting here.  So, tell me one additional thing, If he needs to uncheck possible owner.  All the preferred Owners have to remain checked, don't you? or what does it depend on?

    Warm regards MeVs

    Tuesday, November 5, 2019 6:22 AM
  • You can read more about these options in the link below, they are well described there:

    https://www.altaro.com/hyper-v/how-to-restrict-clustered-hyper-v-virtual-machines-to-specific-cluster-nodes-part-2/


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, November 5, 2019 6:38 AM
  • Than you very much for your quick response. I will certainly do it.

    Warm regards MeVs

    Tuesday, November 5, 2019 6:44 AM