All VMware vSAN certified servers that are mentioned in the VMware HCL can be considered to be a part of the vSAN cluster, which utilizes both magnetic disks and flash disks for capacity and cache tiers. 70% of the available cache is allocated for storing frequently read disk blocks by reducing accesses to the slower magnetic disks, while the remaining 30% of the available cache is allocated to writes. Multiple writes should be coalesced and written sequentially to enhance magnetic disk performance:

1. Choose the cluster that the host servers are added on.
2. Click the Configure... option on the right-hand side to manage all the datastores powered by vSAN:

3. Find the option to configure the vSAN under Virtual SAN.
4. Go to the configuration page.

5. Then, go to Claim disks from datastore, and then choose Manual:

6. Fault Domains & Stretched Cluster: Configure two host vSAN clusters.
7. Confirm that the networking is valid on the vSAN VMkernel adapters.
8. Verify that all of the disks show up for each server.
9. Collapse the disks to their logical drives. Then, set the SSDs to the Cache tier and the HDDs to the Capacity tier.
10. Choose the fault domains and the Preferred fault domain and Secondary fault domain.
11. Click Next and continue.
12. Select the option to choose the witness VM.

13. Map the capacity and the Cache tier for the witness VM host. Then, deploy the witness VM to monitor the vSAN cluster:

14. Click on Finish to complete the vSAN configuration. The disks should now be visible.
15.  Log on to a host server and type the following command:

localcli vsan cluster get

16.  Verify that the cluster shows up as healthy.
17.  Under Cluster | Monitor | VSAN |, run the health check to confirm that the configuration is correct.

We have gone through how to configure a vSAN cluster, as well as how to perform health check monitoring. Now, we will learn about the various policies that we can configure through SPBM.