@VMbkota, how much slack space is advised or required in a cluster varies on a lot of factors.
Some main points that you should consider:
- The capabilities and/or limitations of your cluster layout.
- What type of scenarios do you need or want the data to be able to heal back to a redundant state (and how many times and in what timespans etc.).
- The current and expected future footprint of the storage space (and accounting for any temporary or transient usage).
This is a 3-node cluster - if a node fails then nothing stored as FTT=1 will get repaired back to a redundant state and thus putting aside any space for rebuild from this won't be beneficial, this is why an N+1 configuration e.g. a 4-node (or more) cluster is preferable. If you want the cluster to be able to repair all data from a disk or Disk-Group failure then how much space you should be leaving unused depends on the size of the disks and Disk-Group configuration and also the size and placement of the largest objects in the cluster.
All your data (in the cluster in screenshots anyway) is stored with a 100% thick-provisioned storage policy, if you don't expect to fill and expand or add any more vmdks than current then that has already reserved space for these at their full size. This cluster would be ~25% storage used with thin-provisioned and the current data.
3-node clusters don't have many options for changing storage policies here so you don't really have to worry about slack space for these needing deep reconfiguration of objects (other than changing Stripe-Width).
You have a 19.65TB vsanDatastore there with 6.23TB free, that is ~31.5% free so not sure where vROps is getting '1,77.002 GB' from.
