VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
Note that striping does not guarantee that components get striped across hosts, it
only ensure that components are striped across physical disks. However those disks
could be in different hosts, depending on how Virtual SAN decides to implement the
configuration.
Delta-disks are created when a snapshot is taken of the VM. A delta disk inherits the
same policy as the parent disk, e.g. stripe width, replicas, etc.
The swap object is created only when the virtual machine is powered on.
The memory snapshot object is created when a snapshot is taken of the VM, and a
memory snapshot is also requested.
There are two limits in relation to components in Virtual SAN:
Maximum number of components per host limit in Virtual SAN 5.5: 3000
Maximum number of components per host limit in Virtual SAN 6.0: 9000*
Maximum number of components per object: 64 (this includes stripe width
and replica copies)
* Note that the component count only increases in Virtual SAN 6.0 when the on-disk
format is upgraded to v2.
Components per host includes components from powered off virtual machines.
Virtual SAN distributes components across the various hosts in the cluster and will
always try to achieve an even distribution of components for balance. However
some hosts may have more components than others, which is why VMware
recommends, as a best practice, that hosts participating in a Virtual SAN cluster be
similarly or identically configured. Components are a significant sizing
consideration when designing and deploying a Virtual SAN cluster in 5.5 but not so
much really in 6.0, since the maximums are considerably larger.
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 / 1 2 6