1 person found this helpful
use vmware converter VM to VM inorder to remove that snapshot in a more secure way that commit using snapshot manager
Well you will be pleased to know that you don't have a 900GB+ snap, the quickest and safest way to remove this is to use a V2V conversion, ( assuming you have the space to do so)
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth VCP / vExpert
VMware Communities User Moderator
Contributing author on "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://www.amazon.co.uk/VMware-VSphere-Virtual-Infrastructure-Security/dp/0137158009/ref=sr_1_1?ie=UTF8&s=books&qid=1256146240&sr=1-1]”.
Contributing author on "[VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410|http://www.amazon.co.uk/VMware-Certified-Professional-VSphere-Study/dp/0470569611]”.
looks like ...
The large disk 1 has one snapshot with 178 Mb.
Disk 2 has 2 snapshots each 3 Gb.
Disk 3 has no snapshots
Probably the vmsd file has bad entries so snapshot size is displayed incorrect.
At the moment I would not trust snapshot-manager operations - better clean up first.
You should be really happy to know that you dont have a 900G snapshot. To commit ( consolidate) the other two snapshots you can clone the Vm which is the safest way.
I did just clone the VM and the snapshots were all cleaned up. Doing a V2V would most likely have had the same successful result, but I thought that cloning would be easier!
thanks everyone for the responses.