Deploying new VM using vSAN policy will fail either with PBM error “No VASA Provider for schema namespace (VSAN) found” or “Datastore does not match current VM policy”. Snapshot or backup task may also fail with error “Invalid virtual machine configuration. There are currently 0 usable fault domains. The operation requires 1 more usable fault […]
Read More “vSAN “Datastore does not match current VM policy””
vSAN Health checks can be silenced through UI as well as RVC. Using both methods, we can silence the check and also restore any silent check. Through vSphere UI :- Through vCenter Ruby Console (RVC) :- RVC method uses the check IDs to silence or restore vSAN health checks. To list the status of all […]
Sometimes the ESXi host may stuck for very long time while loading vSAN while ESXi reboot. To isolate the issue from vSAN, you may need to boot the host without vSAN. Note: This may not be a feasible option if the data still exists on the host and the objects do not have sufficient raid […]
Sometimes you may see few objects in Inaccessible state in vSAN cluster. Any disruptive action like abrupt power failure, or swap objects could be the reason for inaccessible objects.If the objects are no longer needed, we can check and get rid of them. SSH into vCenter and browse to vSAN cluster in RVC : Run […]
vSAN provides feature to encrypt the data at rest. Below are pre-requisites to enable vSAN encryption – You will need a Key Management Server (KMS) vCenter should establish a trusted connection with the KMS server and vice versa User should have privileges on vCenter :Host.Inventory.EditClusterCryptographer.ManageEncryptionPolicyCryptographer.ManageKMSCryptographer.ManageKeys To enable encryption, Go to cluster -> Configure tab -> […]
