none
Hyper-v Failover win server 2016 best practice RRS feed

  • Question

  • Hi all,

    We are planning to create a hyper-v cluster on two identical Dell PowerEdge R740 Server  with 256 GB of memory.

    My questions is what's the best practice to create the cluster ? 

    Regarding

    -Networks

    -Quorum Disk size 

    - Performance of Server Memory - CPU 

    and if there any thing else should i take care about 

    Thanks in advance

     



    IT Helpdesk

    Thursday, May 23, 2019 1:15 AM

All replies

  • Hi ,

    >>Networks

    For how to configure windows failover cluster networks, please refer to the following link:

    Configuring Windows Failover Cluster Networks

    Best Practices on Setting up Hyper-V Cluster Networks in Windows Server 2016

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    >>Quorum Disk size 


    For your reference:

    Configure and manage quorum

    Quorum Drive Configuration Information

    >>Performance of Server Memory - CPU 

    Virtual machines cannot be live migrated or saved and restored across virtualization hosts that use processors from different CPU manufacturers.
    If you plan to move virtual machines, without rebooting them, between virtualization hosts that may use different generations of processors, you should enable processor compatibility mode.

    For your reference:

    Processor Compatibility Mode in Hyper-V

    The different CPU's speed does not prevent you to create a cluster. But think about that you have two node cluster with heavy load to them. One node has a powerful CPU and the other node not. If the node with the powerful CPU fails, can the other node handle the heavy workload?

    General speaking, we recommend that you use the identical hardware on all the nodes.

    I would think using of Identical machines (same HW, Proc, RAM, OS & service pack etc) in cluster environment is the best practice.

    Best Regards,

    Candy


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

    Thursday, May 23, 2019 3:07 AM
  • Hi ,

    Just want to confirm the current situations.

    Please feel free to let us know if you need further assistance.                    

    Best Regards,

    Candy


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

    Friday, May 24, 2019 7:45 AM
  • Thanks Candy for your reply

    Our server has a four port network adapter 2x 1g and the other two ports is 10g and unforenatly the two 10 g ports not supported by network team so we only have two ports 1g 

    so how i can use them with hyper-v cluster?

    • Edited by MandoesaM Saturday, May 25, 2019 12:43 PM
    Friday, May 24, 2019 1:31 PM
  • Hi ,

    >>Our server has a four port network adapter 2x 1g and the other two ports is 10g and unforenatly the two 10 g ports not supported by network team so we only have two ports 1g 

    Thanks for your updating.

    You could configure four networks without NIC team or configure three networks with one NIC team.

    Four networks (the standard networks):

    - Cluster Network

    - Live migration

    - Storage Network

    - Management Network

    ======================================================

    Three networks:

    - Cluster Network

    - Storage Network

    - Public network

    =======================================================

    For your reference:

    Windows Server Hyper-V Cluster Networks

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Best Regards,

    Candy


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


    Monday, May 27, 2019 2:35 AM
  • Hi Candy,

    Thanks for your reply

    Can i create NIC teaming on two adapter 1 Gigabit?? if not what's your proposed solution to create the Virtual switch

    one network adapter for (Managament-LiveMigration-Cluster)

    and the other network for ISCSI Only

    Thanks

     

    Monday, May 27, 2019 12:51 PM
  • Hi ,

    >>Can i create NIC teaming on two adapter 1 Gigabit??

    Yes, you could. Generally speaking, it all depends on your environment.

    If the live migration traffic and Cluster Shared Volume traffic is not too high, as you said, you could configure the following network:

    - 10g NIC  ISCSI Only

    - 10g NIC  Managament-LiveMigration-Cluster

    - NIC team 2G  Service Network(VM)

    Best Regards,

    Candy


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

    Tuesday, May 28, 2019 2:46 AM
  • Hi ,

    Just want to confirm the current situations.

    Please feel free to let us know if you need further assistance.                  

    Best Regards,

    Candy


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

    Thursday, May 30, 2019 7:39 AM
  • You can find a step by step guide for 2-nodes cluster configuration here: https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyper%D1%81onverged-scenario-with-windows-server-2016

    Make sure that you have a dedicated networks for each purpose (Management, Live Migration, VMs, etc). It is enough to configure 1 GB Quorum size in most cases.

    As for the performance question, make sure that you are using thick disks for VMs (if VM is performance hungry) and the total amount of RAM, assigned to VMs is not exceeding the RAM size installed on the host.

    Thursday, May 30, 2019 2:35 PM
  • Hi ,

    Did you have any updates on this question?

    Best Regards,

    Candy


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

    Friday, May 31, 2019 8:20 AM