Skip to main content

Task 04: Storage Performance Validation

Implementation Part 7

DOCUMENT CATEGORY: Implementation Runbook
SCOPE: The storage of a deployed Azure Local cluster
PURPOSE: Check pool, disk and volume health and capacity, and optionally measure latency
MASTER REFERENCE: Storage Spaces Direct overview

Status: Active

The VMFleet baseline of Part 6 task 02 is the performance acceptance test. This task is the quick health and capacity read for the handover and after changes; with -RunPerformanceTest it also writes and reads a test file on each volume. That generates I/O on the cluster: run it in a maintenance window on a production cluster.


Values from infrastructure.yml​

The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.

KeyWhat the script does with it
cluster.nameThe cluster to test

The limits (-CsvUsageWarningPercent, -MaxAvgWriteLatencyMs, -MaxAvgReadLatencyMs) are parameters, not values of a deployment.


Execution Options​

PowerShell on a cluster machine​

Get-StoragePool -IsPrimordial $false; Get-VirtualDisk; Get-PhysicalDisk
Get-ClusterSharedVolume | Select-Object Name, State, OwnerNode

Validation​

  • Exit code 0, every pool and virtual disk Healthy
  • Every volume Online and below the usage limit
  • With -RunPerformanceTest: latency below the limits

Troubleshooting​

IssueCauseResolution
A volume is above the usage limitThe volume is fillingExtend it, or move data; plan capacity (Task 04 of Part 8, Capacity)
A virtual disk is WarningA repair job is runningGet-StorageJob; wait
Latency is above the limitThe cluster is busy, or a disk is slowRun it again in a quiet window; check Get-PhysicalDisk

PreviousUpNext
Task 03: Network ConfigurationPart 7 IndexTask 05: Deployment Documentation

Version Control​

VersionDateAuthorChanges
1.0.02026-11-15Azure Local CloudInitial release. The script reads cluster.name from infrastructure.yml (it was -ClusterName)