What a shame guys... this functionality arrivd with vSAN 6.7 and later.
But the vSAN must be all-flash architecture so - BC
(D. TRIM and UNMAP is enabled.) is not a prerequisite because enabling TRIM and UNMAP is a configuration step rather than a prerequisite.
C&D are correct - B is wrong because OSA also it support without all flash architecture.
TRIM/UNMAP Configuration
Enabled by default on vSAN ESA and disabled by default on vSAN OSA,
vSAN Cluster > Configure > Services > Advanced Options
C D. https://core.vmware.com/resource/vsan-space-efficiency-technologies#:~:text=To%20enable%20TRIM%2FUNMAP%20for,connect%20to%20the%20RVC%20console.&text=Next%2C%20browse%20to%20compute%2C%20and%20identify%20the%20cluster%20name.&text=Next%2C%20enable%20unmap%20support.&text=Once%20enabled%2C%20there%20are%20several,reclaim%20no%20longer%20used%20capacity.
TRIM/UNMAP Space Reclamation
In an attempt to be more efficient with storage space, modern guest OS file systems have had the ability to reclaim no longer used space using what are known as TRIM/UNMAP commands for the respective ATA and SCSI protocols. vSAN has full awareness of TRIM/UNMAP commands sent from the guest OS and can reclaim the previously allocated storage as free space. This is an opportunistic space efficiency feature that can deliver much better storage capacity utilization in vSAN environments.
VMware Specific Guidance
In vSAN 8, TRIM/UNMAP can be enabled in the User Interface, under the services enablement
https://core.vmware.com/resource/vsan-space-efficiency-technologies#sec19560-sub6
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
VMWare_Admin
3 months agoKartik
8 months agoShiVip
11 months agoMarlonC
1 year, 1 month agojchampion
1 year, 2 months agolibraboysg
1 year, 2 months agoSTONE84
1 year, 3 months ago