Fairly new to the discussions,
I have noticed that when I upload a thin provisioned vmdk to a NFS datastore via the Vsphere web client and then use the Vsphere web client GUI to then copy the vmdk from a NFS datastore to a normal VMFS datastore, it gets inflated as a thick provisioned vmdk.
My question is, is this normal behaviour for a thin provisioned vmdk copy type function to get inflated to a thick provisioned vmdk once the copy is completed. I have also noticed that the Vsphere web client GUI move function acts in the same manner as the Vsphere web client GUI copy function.
I have looked at documentation and its not clear as to what the actual copy function does to the vmdk.
Thanks for reading and also helping out if you can to understand this behaviour and let me know if you need any more clarity o the question.
ESXI host version = 6.7
vSphere Client version 18.104.22.168000
Are you using a storage vmotion for it? Did you know that during that migration you will be able manually to choose if disk should be thin or thick. lazy or eager zeroed.