none
Shut down all Hosts without HA moving the VMs

    Question

  • Hello
    We are going to perform maintenance on our entire Server-Blade system witch contains 5 Hyper-V hosts (win 2008R2 core) and 4 physical DB-servers. We are upgrading the Blade's NIC's to 10Gb.

    To do this I will need to shut down all physical servers including the Hyper-V hosts but I do not want the vm's to perform the automatical HA move of wm's during this Maintenace.

    So my questions are:
    What is the best way to shut down all hosts without moving the vm's?
    Can I put the HA in "Maintenace mode" or temporarily disable it?
    Do I need to put the Hosts in Maintenace mode ?

    /Anders

    Sunday, April 21, 2013 6:38 AM

Answers

  • Hi,

    You can firstly pause these Hyper-V nodes. When you pause a node, existing groups and resources stay online, but additional groups and resources cannot be brought online on the node.

    After you pause all these nodes, you can place Windows Server 2008 R2 Hyper-V cluster node server to maintenance mode, these action will pause all virtual machines on the host into a saved state.

    Then stop cluster service, shutdown Hyper-V host server and do your hardware update.

    For more information please refer to following MS articles:

    Windows Server 2008 R2 Hyper-V cluster maintenance mode
    http://technet.microsoft.com/en-us/library/ee236427.aspx#MaintenanceMode
    Start or Stop the Cluster Service on a Cluster Node
    http://technet.microsoft.com/en-us/library/cc771742.aspx
    Pause or Resume a Node in a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc731291.aspx

    Hope this helps!

    TechNet Subscriber Support

    If you are TechNet Subscription

    Lawrence

    TechNet Community Support

    Monday, April 22, 2013 5:26 AM
  • Hi Anders,

    you can shut down all your virtual machines via the Hyper-V or Cluster Manager.
    After that, shut down the cluster (either via PowersHell or Remote Cluster Manager).

    As you are going to shutdown all your cluster nodes, make sure that "auto-restart" is disabled for the VMs. It's not so nice if they all start-up at the same time ;-)

    Best Regards,
    Jens


    jensit.wordpress.com

    Monday, April 22, 2013 1:53 PM
  • Sorry for my late reply.
    I want to thank you for your replies.
    I have read the Articles and from that and some google searches I have
    come to this conclusion (If I have understood everything right)

    These are the steps I should do (in this order).
    1. in Failover Cluster Manager, Disable Aoutostart on all VM's on each node
    2. in Hyper-V Manager, Shut down all WM's
    3. in Failover Cluster Manager, shut down Cluster
    4. Shot down all Hosts
    5. do Maintencance
    6. Start all Hosts
    7. in Failover Cluster Manager, Start Cluster
    8. in Hyper-V Manager, Start all WM's
    9. in Failover Cluster Manager, Enable Aoutostart on all VM's on each node

    Thank you
    Anders


    Friday, April 26, 2013 12:25 PM

All replies

  • Hi,

    You can firstly pause these Hyper-V nodes. When you pause a node, existing groups and resources stay online, but additional groups and resources cannot be brought online on the node.

    After you pause all these nodes, you can place Windows Server 2008 R2 Hyper-V cluster node server to maintenance mode, these action will pause all virtual machines on the host into a saved state.

    Then stop cluster service, shutdown Hyper-V host server and do your hardware update.

    For more information please refer to following MS articles:

    Windows Server 2008 R2 Hyper-V cluster maintenance mode
    http://technet.microsoft.com/en-us/library/ee236427.aspx#MaintenanceMode
    Start or Stop the Cluster Service on a Cluster Node
    http://technet.microsoft.com/en-us/library/cc771742.aspx
    Pause or Resume a Node in a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc731291.aspx

    Hope this helps!

    TechNet Subscriber Support

    If you are TechNet Subscription

    Lawrence

    TechNet Community Support

    Monday, April 22, 2013 5:26 AM
  • Hi Anders,

    you can shut down all your virtual machines via the Hyper-V or Cluster Manager.
    After that, shut down the cluster (either via PowersHell or Remote Cluster Manager).

    As you are going to shutdown all your cluster nodes, make sure that "auto-restart" is disabled for the VMs. It's not so nice if they all start-up at the same time ;-)

    Best Regards,
    Jens


    jensit.wordpress.com

    Monday, April 22, 2013 1:53 PM
  • Hi,

    I would like to confirm what is the current situation? Have you resolved the problem or do you have any further progress?

    If there is anything that we can do for you, please do not hesitate to let us know, and we will be happy to help.


    Lawrence

    TechNet Community Support

    Thursday, April 25, 2013 5:19 AM
  • Hi,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as 'Answered' as the previous steps should be helpful for many similar scenarios.

    If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

    In addition, we'd love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks!


    Lawrence

    TechNet Community Support

    Friday, April 26, 2013 9:11 AM
  • Sorry for my late reply.
    I want to thank you for your replies.
    I have read the Articles and from that and some google searches I have
    come to this conclusion (If I have understood everything right)

    These are the steps I should do (in this order).
    1. in Failover Cluster Manager, Disable Aoutostart on all VM's on each node
    2. in Hyper-V Manager, Shut down all WM's
    3. in Failover Cluster Manager, shut down Cluster
    4. Shot down all Hosts
    5. do Maintencance
    6. Start all Hosts
    7. in Failover Cluster Manager, Start Cluster
    8. in Hyper-V Manager, Start all WM's
    9. in Failover Cluster Manager, Enable Aoutostart on all VM's on each node

    Thank you
    Anders


    Friday, April 26, 2013 12:25 PM
  • Hi,

    Thanks for sharing your experience!

    You experience and solution can help other community members facing similar problems.

    Thanks for your contribution to Windows Server Forum!

    Have a nice day!

    Lawrence

    TechNet Community Support

    Monday, April 29, 2013 2:53 AM