Cluster creation and enabling Storage Spaces Direct configuration on the cluster creates only a storage pool and does not provision any virtual disks in the storage pool. Use the New-Volume cmdlet to provision new virtual disks as the cluster shared volumes for the Azure Stack HCI cluster.
When creating volumes in the Azure Stack HCI cluster infrastructure:
- Ensure that you create multiple volumes—a multiple of the number of servers in the cluster. For optimal performance, each cluster node should own at least one virtual disk volume. Virtual machines (VMs) on each volume will perform optimally when running on the volume owner node.
- Limit the number of volumes in the cluster to 32 on Windows Server 2016 and 64 on Windows Server 2019 and the Azure Stack HCI operating system.
- Ensure that the storage pool has enough reserve capacity for any in-place volume repairs arising out of failed disk replacement. The reserved capacity should be at least equivalent to the size of one capacity drive per server and up to four drives.
For general guidance on planning volume creation, see Planning volumes in Storage Spaces Direct.
- On Windows Server 2016, Windows Server 2019, and the Azure Stack HCI operating system clusters with three or more nodes—Three-way mirror
- On Windows Server 2019 and Azure Stack HCI operating system clusters with four or more nodes—Three-way mirror or mirror-accelerated parity