Hi.
Recently, Developer Team's give me three files (.ovf, .nvram, .vmdk). Usually, I upload these three files in my vCenter and create a new virtual machine. Buy in this case, .vmdk is large (800GB) and I think that the original vmdk has 4TB, and the upload process delay a lot.
Five days before the process started, I see like in data store there is a vmdk file with 800GB, but the process doesn't stop. Is possible that the vmdk file has to grow up until 4TB? Is there any procedure to do this locally over ESX server for it was easier and faster?
Regards
Hi,
Use "OVF Tool" for this process. I think that "OVF Tool" is much better than uploading via web client.
About disk size, because VMDK file stored as thin disk, the file is containing of data and not free blocks. But if VMDK must be as thick disk on virtual machine configuration, then it should be converted to thick disk during deployment. I guess that the disk was eager-zeroed.
Here is the link to download latest version of Ovftool along with the user's guide for reference.
https://developer.vmware.com/web/tool/4.4.0/ovf