Plan cluster volume count around metadata ownership and capacity

Source facts

Microsoft relates the number of cluster volumes to pool capacity and the maximum supported volume size, with at least one volume per node. That layout allows volume ownership to be distributed among servers; one server coordinates metadata for each volume. The planning guidance treats filesystem, resiliency, and size as separate choices driven by workload performance and capacity needs. Microsoft documentation.

Applicability

Inventory the pool, node count, workload groups, expected growth, and supported volume limits. Review the specific resiliency and capacity calculation for the proposed design before assigning a target size to each volume.

DSE recommendation

Create a volume worksheet showing workload placement, planned capacity, and intended ownership distribution. Ask the application and storage owners to approve the boundaries between workloads. Include the expected expansion scenario so the initial layout does not depend on an undocumented spare-capacity assumption.

Verification

Compare the created volume inventory and ownership with the worksheet. Test representative access and an approved ownership move while observing the workload. Record actual capacity and distribution separately from forecasts, and revisit the plan when node count or workload growth changes materially.

Official references

Microsoft Learn: Plan volumes on Azure Local and Windows Server clusters. Source reviewed September 8, 2026.