Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
E2E Deployment and Operations Guide with Scalable Networking: Microsoft HCI Solutions from Dell Technologies
About using this guide Deployment Introduction Solution Overview Solution Deployment Scalable Architecture with Network ATC GPU Integration Day 1 operations Managing and monitoring clusters with Windows Admin Center Dell OpenManage Integration with Windows Admin Center
Dell OpenManage Integration with Windows Admin Center
Overview
Prerequisites for managing AX nodes
Installing the OMIMSWAC license
Managing Microsoft HCI-based clusters
Overview Prerequisite checks Health status Inventory Locating physical disks and viewing their status Viewing update compliance and updating the cluster
Full Stack Cluster-Aware Offline Updating
Full Stack Cluster-Aware Updating for Azure Stack HCI clusters
Updating a standalone node before adding it to the cluster
Enabling hardware alerts for HCI cluster
Secure cluster with Secured-core
Enabling operating system features
Protect your infrastructure with infrastructure lock
Enable or disable infrastructure lock
Manage CPU cores in Azure Stack HCI clusters
Expanding cluster from two nodes to three-node+ cluster
Validate and remediate Azure Stack HCI clusters
View HCP compliance summary
Onboard Dell policies to Azure Arc from Windows Admin Center
View recommendations for storage expansion
View node level storage configuration details
Known issues
Updates and maintenance Secure connect gateway References

Expanding cluster from two nodes to three-node+ cluster

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > Guides 22H2 and earlier > E2E Deployment and Operations Guide with Scalable Networking: Microsoft HCI Solutions from Dell Technologies > Expanding cluster from two nodes to three-node+ cluster

Expanding cluster from two nodes to three-node+ cluster

  • Azure Stack HCI version 22H2 supports inline fault domain and resiliency changes for scaling-out Azure Stack HCI cluster from two nodes to three-node+ cluster.

    • The new node must be installed with an operating system same as the cluster. In this case, it should have Azure Stack HCI version 22H2 operating system.
    • Only two-way to three-way mirror volume resiliency is supported for cluster expansion.
    1. Create an Azure Stack HCI cluster with two nodes. Check the resiliency for volumes using the following command:Get-VirtualDisk | Select NumberOfDataCopies, FriendlyName
      To view the volume resiliency on the Windows Admin Center, select the cluster name and click Volumes > Inventory. All volumes must have a two-way mirror resiliency.
      Screen shot of the Inventory tab

    2. Expand the cluster (add one (or more) new nodes) using the following command:Add-ClusterNode -Name <nodename>
    3. Convert the volume resiliency from two-way to three-way mirror using the following command:Set-VirtualDisk -FriendlyName <name> -NumberOfDataCopies 3
      After running this command, check the cluster name and click Volumes > Inventory. The volume status will show as Needs repair. You can also monitor the status by using the Get-StorageJob command on the nodes.
      Screen shot of the Inventory tab

      After converting all the volumes:


      Screen shot of the Inventory tab

      For more details, visit Single server scale-out for Azure Stack HCI version 22H2 - Azure Stack HCI | Microsoft Learn.