A small Hyper-V Storage Spaces Direct (S2D) cluster can provide resilient shared storage and failover for virtual workloads. This guide covers a practical baseline build sequence.
Target architecture
- 2–4 Hyper-V nodes (lab/small production pattern)
- Windows Server Datacenter edition
- Validated storage/network hardware for S2D
- Failover Cluster + Cluster Shared Volumes (CSV)
1) Prepare hosts consistently
- Same OS build and patch level on all nodes
- Enable required roles/features (Hyper-V, Failover Clustering)
- Configure identical networking, DNS, and time sync
2) Validate cluster readiness
Test-Cluster -Node HV01,HV02 -Include "Storage Spaces Direct",Inventory,Network,"System Configuration"Resolve all critical validation issues before proceeding.
3) Create failover cluster
New-Cluster -Name S2D-Cluster -Node HV01,HV02 -StaticAddress 10.0.0.50
4) Enable Storage Spaces Direct
Enable-ClusterS2D5) Create storage volume
New-Volume -StoragePoolFriendlyName "S2D on S2D-Cluster" -FriendlyName "CSV-VMs" -FileSystem CSVFS_ReFS -Size 2TB -ResiliencySettingName Mirror6) Deploy and validate VMs
- Create test VM on CSV volume
- Run live migration/failover tests
- Confirm storage/network performance under load
Operational best practices
- Use dedicated networks for management, storage, and live migration
- Keep firmware/drivers aligned across nodes
- Monitor cluster health and disk alerts proactively
- Back up cluster config and VM workloads regularly
This sequence gives a stable small S2D cluster foundation for Hyper-V virtualization.
