An overview of vSAN objects and components
When you create VMs in a VxRail cluster, you must specify the vSAN storage policy (we will discuss the details in the next section) for each VM. It will automatically create each object’s vSAN component (that is, the VMDK) and allocate it to each VxRail node when you apply the vSAN storage policy to the VM. vSAN manages and stores data called objects. Each object on the vSAN datastore includes data, metadata, and a unique ID. The most common vSAN objects are the VDMKs. In traditional storage, you need to define the storage pools, the RAID level protection, and the hot spare. Then, you can create VMs or build your application into this storage. All storage configurations must be completed on day one. The vSAN architecture is different from traditional storage. vSAN objects are made of components determined by vSAN storage policies. You can change or update the Failure Tolerance Method (FTM) and Failures To Tolerate (FTT) of the VM at...