Confirm the symptom
Use vCenter performance charts to identify read, write and device latency. Determine whether the problem affects one datastore, one host or multiple hosts.
Check ESXi paths
Review storage adapters, paths and multipathing status. A degraded path or repeated path changes can create instability.
Check queueing
Look for sustained queue depth and device latency. High latency with high I/O demand may indicate workload saturation rather than a connectivity failure.
Check the storage array
Correlate the vSphere timestamp with array controller, disk group, cache and replication metrics. Storage-side contention is often visible only in the array tools.
Check VM workload
Identify VMs generating high IOPS, backup activity, snapshot operations and storage-intensive jobs.
Validate recovery
Confirm latency returns to normal, paths are healthy and affected VMs no longer report storage timeouts.
More practical infrastructure guides
Browse the TechRunbook article library for Windows Server, VMware, Hyper-V, Azure, PowerShell and MABS troubleshooting.
Browse all articles →