none
Hyper-v 2019 clusters? how do we set up the clusters and storage?

    Question

  • We want to create a very large hyper-v 2019 cluster ( thinking 64 nodes is the maximum).

    We do not have a SAN/ NAS therefore is there a solution using disks attached directly to each server node?

    How do we go about installing hyper-v 2019 cluster in the Azure Cloud?

    Also if a VM is in one cluster set can it be moved to another cluster set?  What happens if you need the VM to move off a cluster set where you have resource contention issue?

    What is the minimum resources (CPU, RAM) required for a hyper-v 2019 cluster node to function?,... keep in mind this hyper-v server resources cannot have adverse effects on this hosted VM/s.


    dsk

    Tuesday, December 25, 2018 10:09 PM

All replies

  • Hi,

    Thanks for your question.

    1)is there a solution using disks attached directly to each server node?

    Yes, your need can be implemented if it is similar as this thread (https://community.spiceworks.com/topic/1912333-windows-server-2016-sterch-cluster-with-local-disks ).

    We could deploy by referring to this docs,

    https://docs.microsoft.com/en-us/windows-server/storage/storage-replica/stretch-cluster-replication-using-shared-storage

    In this evaluation example, you will configure these computers and their storage in a single stretch cluster, where two nodes share one set of storage and two nodes share another set of storage, then replication keeps both sets of storage mirrored in the cluster to allow immediate failover. These nodes and their storage should be located in separate physical sites, although it is not required.

    2)How do we go about installing hyper-v 2019 cluster in the Azure Cloud?

    Regarding to this deployment, Please refer to these docs,

    https://docs.microsoft.com/en-us/windows-server/failover-clustering/deploy-cloud-witness

    https://argonsys.com/learn-microsoft-cloud/library/configuring-cloud-witness-in-windows-server-2016-cluster-azure-files-cloud-azure-winserv/

    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.

    3)Also if a VM is in one cluster set can it be moved to another cluster set?  What happens if you need the VM to move off a cluster set where you have resource contention issue?

    Based on my experience, it can be implemented, due to clustered VMs can move between different individual clusters even if without cluster sets deployment. Because of the resource limitation, we can not test this deployment, we could refer to the following MS docs which in detail discussed Cluster Sets,

    https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/cluster-sets

    4)What is the minimum resources (CPU, RAM) required for a hyper-v 2019 cluster node to function?

    Please refer to this docs for the details you’d like to know,

    https://docs.microsoft.com/en-us/windows-server/get-started-19/sys-reqs-19

    Unless otherwise specified, these minimum system requirements apply to all installation options (Server Core, Server with Desktop Experience, and Nano Server) and both Standard and Datacenter editions. Unless otherwise specified, these minimum system requirements apply to all installation options (Server Core, Server with Desktop Experience, and Nano Server) and both Standard and Datacenter editions.

    Hope above information can help you. If you have any question or concern, please feel free to let me know.

    Best regards,

    Michael


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

    Wednesday, December 26, 2018 4:21 AM
    Moderator
  • "We do not have a SAN/ NAS therefore is there a solution using disks attached directly to each server node?"

    Microsoft has a clustering solution that uses shared storage.  It is called Storage Spaces Direct (S2D).  See https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-overview for an overview.  However, it does not support 64 nodes.

    Though a non-S2D cluster can support up to 64 nodes using some sort of externally shared storage, there are very few of these installed.  More nodes increases the complexity and management.  It works, but few organizations have found a benefit of a single 64-node cluster versus four 16-node clusters or eight 8-node clusters.  I am curious why you are looking at such a large cluster.

    "Also if a VM is in one cluster set can it be moved to another cluster set?  What happens if you need the VM to move off a cluster set where you have resource contention issue?"

    Yes, Microsoft provides the ability to migrate VMs between clusters or between clusters and stand-alone hosts.


    tim

    Wednesday, December 26, 2018 3:24 PM
  • Hi,

    Could the above reply be of help? If yes, you may mark it as answer, if not, feel free to feed back.

    Best Regards,

    Michael


    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, December 31, 2018 7:40 AM
    Moderator