VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
Understanding components and component count
Note: The component limit per host was 3,000 for Virtual SAN version 5.5. Virtual SAN
Version 6.0 increased this limit count to 9,000.
The disk limits are worth noting regularly via the vsan.check_limits RVC
command to ensure that the limits are not being reached.
In this example, a test VM using the following VM Storage Policy settings has been
deployed:
Number of Failures to Tolerate (FTT) = 1
Number of Disk Objects to Stripe (SW) = 2
The way this virtual machine’s object are deployed and distributed across the
Virtual SAN cluster is looked at next, as well as verifying that the policy has indeed
taken effect.
Examining components via the vSphere web client
One can examine some of the components via the vSphere web client, and in this
example (using vSphere 5.5), they show the following layout for the VM Home
Namespace and the VMDK. Here is the VM Home Namespace object and its
components:
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 90