

The small one with the name “ xxxxx-000002.vmdk” has the size of 300G. And when checking the datastore, we saw two vmdk listed, the big one has the size of 2T but not used. However, we did see the hard drive having the disk file name like “ xxxxx-000002.vmdk” in the settings of the VM. When we looked around within vSphere web GUI, we didn’t see any snapshots listed.

That disk is the only hard drive allocated from this datastore.

We could see one of datastores was full that’s because we were copying a large amount of data over from another system to one of disks on this VM. However the VM was hanging and it would not start after a reboot. A snaptshot was taken and then deleted after 3 days. After the upgrade is done and the system/application has been verified running fine for a few days, the snapshot needs to be deleted to release space. It’s a best practice to take a snapshot when doing an upgrade for either OS or application running on a virtual machine.
