Query about Thin Provisioning and Thick Provisioning

Solution 1:

vSphere write whole capacity with “0” with “thick provisioned eager zeroed”. It means, that the storage on LUN should be reserved, because all of the allocated blocks are rewritten. But, if backend storage supports deduplication and/or compression, “zeroed” vmdk takes small amount of space on SAN due to extreme high deduplication ratio of “0”-blocks. So, after the writing of “real” data on vmdk, the deduplication ratio will decrease and it can be a risk of lack of storage, because of overprovisioning. Here a good article, how storage provisioning works in vSphere - https://www.vmwareblog.org/vmware-esxi-disk-provision-work-difference-one-better/