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. The New-Volume cmdlet can be used to provision new virtual disks and in turn provision them 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. Limit the number of volumes in the cluster to 32 on Windows Server 2016 and 64 on Windows Server 2019.
• 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 for volume creation in Storage Spaces Direct, see https://docs.microsoft.com/windows-server/storage/storage-spaces/plan-volumes.

Note: We recommend that you use the following resiliency settings when you create virtual disks:

• On Windows Server 2016 and Windows Server 2019 clusters with three or more nodes—Three-way mirror
• On Windows Server 2019 clusters with four or more nodes—Three-way mirror or mirror-accelerated parity