the longer you keep the snapshot the longer it takes to remove it.
Snapshots take the vmdk and make it read only and creates files that keep track of all the changes to the vm since the snapshot was taken.
Deleting a snapshot merges those files back into the vmdk.
I have had the GUI say deletion has timed out. But it is really still deleting . The bad thing is you can not edit any vm settings while it is deleting (i.e. disconnect network card.)
Your free space on you lun will also start to get used and if it fills up your VM will fail.
Through experience I have found you should delete snapshots as soon as you can.
Let's say you have a 400GB storage location for a single ESX Server, how much space do you recommend keeping free for snapshots, file operations, etc.?
On this storage location, how many VMs (say they are all 20GB on one C:\ partition) would you recommend creating?
Would you recommend a different used / free space ratio for a larger SAN storage space?
Snapshots take long time to commit - http://www.vmware.com/community/thread.jspa?threadID=74669
Snapshots take long time to commit - http://www.vmware.com/community/thread.jspa?messageID=584324��
Snapshots take long time to commit - http://www.vmware.com/community/thread.jspa?threadID=73553
Beware the long snapshot - http://www.vmwarez.com/2006/11/beware-long-snapshot.html
Snapshot disk space and growth - http://www.vmware.com/community/thread.jspa?threadID=85409
Fyi if you find this post helpful, please award points using the Helpful/Correct buttons.
Visit my website: http://vmware-land.com