Using Azure Stack HCI on a single server
Applies to: Azure Stack HCI, version 22H2
This article provides an overview of running Azure Stack HCI on a single server, also known as a single-node cluster. Using a single server minimizes hardware and software costs in locations that can tolerate lower resiliency. A single server can also allow for a smaller initial deployment that you can add servers to later (scaling out).
Along with the benefits mentioned, there are some initial limitations to recognize.
- You must use PowerShell to create the single-node cluster and enable Storage Spaces Direct.
- Single servers must use only a single drive type: Non-volatile Memory Express (NVMe) or Solid-State (SSD) drives.
- Stretched (dual-site) clusters aren't supported with individual servers (stretched clusters require a minimum of two servers in each site).
- To install updates for single-node clusters, see Updating single-node clusters. For solution updates (such as driver and firmware updates), see your solution vendor.
- Operating system or other updates requiring a restart cause downtime to running virtual machines (VMs) because there isn't another running cluster node to move the VMs to. We recommend manually shutting down the VMs before restarting to ensure that the VMs have enough time to shut down prior to the restart.
Prerequisites
- A server from the Azure Stack HCI Catalog that's certified for use as a single-node cluster and configured with all NVMe or all SSD drives.
- An Azure Subscription.
For hardware, software, and network requirements see What you need for Azure Stack HCI.
Comparing single-node and multi-node clusters
The following table compares attributes of a single-node cluster to multi-node clusters.
| Attributes | Single-node | Multi-node |
|---|---|---|
| Full software-defined data center (SDDC) stack (hypervisor, storage, networking) | Yes | Yes |
| Storage Spaces Direct support | Yes | Yes |
| Software Defined Networking (SDN) support | Yes | Yes |
| Native Azure Arc integration | Yes | Yes |
| Managed through Windows Admin Center and Azure portal | Yes | Yes |
| Azure billing/registration | Yes | Yes |
| Charged per physical core | Yes | Yes |
| Support through Azure | Yes | Yes |
| Connectivity (intermittent or connected) | Yes | Yes |
| Azure benefits on Azure Stack HCI | Yes | Yes |
| Activate Windows Server Subscriptions | Yes | Yes |
| Azure Defender and Secured-core | Yes | Yes |
| Azure Virtual Desktop | Yes | Yes |
| Azure Site Recovery | Yes | Yes |
| Azure Stack HCI: Stretch cluster support | No | Yes |
| Use Graphics Processing Units (GPUs) with clustered VMs | Yes | Yes |
Known issues
The following table describes currently known issues for single-node clusters. This list is subject to change as other items are identified, check back for updates.
| Issue | Notes |
|---|---|
| SBL cache isn't supported in single-node clusters. | All-flash, flat configuration with Non-volatile Memory Express (NVMe) or Solid-State Drives (SSD) must be used. |
| Windows Admin Center doesn't support creating single-node clusters. | Deploy single server with PowerShell. |
| Windows Admin Center cosmetic user interface (UI) changes needed. | Doesn't limit Live Migration within the same cluster; allows affinity rules to be created, etc. Actions will fail without any harm. |
| Windows Admin Center pause server fails since it tries to drain the server. | Utilize PowerShell to pause (suspend the server). |
| Cluster Aware Updating (CAU) doesn't support single-node clusters in 21H2. You'll need to update to 22H2. | Update using Windows Admin Center (through server manager), PowerShell, or the Server Configuration tool (SConfig). Learn more |