While working with VMWare support on case 1159631091 we had to clone a VM that had 3 seperate HD located on seperate volumes to a temporary large volume and then when after successfully starting the VM we cloned the VM back with appropriate VMDK going back to their original Volumes.. These volumes were thin provisioned and were orignally reporting proper sizes. Now after cloning the volumes are showing completely full.
Example
Volume 1 has a VMDK file of 20GB on a 25GB volume and the volume is showing 24.5GB full on the SAN. it is counting both the 20GB VMDK file and the Ram file of 4GB.
Volume 2 has a VMDK file of 150GB on a 150GB volume. The data on the volume is only about 10GB at this time. Previously my SAN only reported the usage at 10GB and thus I assume the VMDK file was appropriate sized.
Volume 3 has a VMDK file of 50GB on a 50GB volume. There currently is no data on this volume. Previously my SAN reported zero usage.
So I need to know if possilbe and how to shink the VMDK files to their appropriate size so they are reporting properly on my SAN.
Thanks,