Hi Experts,

actual I clean up an old ESX 3.5 Environment i.e. delete old snapshots.

Maybe caused by much ESX overload, within the second Deletion I obtain a timeout error.

In snapshotmanager there are no further snapshots but in vmfs file system on esx host i determine some curios files:


where nnnnn is an ongoing number

How can i delete snapshots finally?

reredokIT ConsultantAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Deleting snapshots may take few hrs or whole day depending on the number of snapshots and size of each
Just wait mate...time out is perfectly normal after 15mins in vCenter
You can monitor the progress in console or ssh
Refer to http://kb.vmware.com/kb/1007566
reredokIT ConsultantAuthor Commented:
elapsed 10hours and more.

ominous: (see image)
that looks like a 13gb snap you're trying to commit.  I'd go home and check it again in the morning :)
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Don't delete the delta files. your current state will be lost.
As mentioned, go home, check it in the morning.
You actually have 2 snapshots.
the 0001 delta is 13 GB and the 0002 delta is 9 GB.
If when you get in the snapshots are still there you have other options..
Let us know how you go.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Paul SolovyovskySenior IT AdvisorCommented:
I have had this on several occastions and vmware support suggested to do a V2V using vConverter since deleting large snapshots has a high failure rate
reredokIT ConsultantAuthor Commented:
V2V a virtual machine in a "virtual" machine?
Paul SolovyovskySenior IT AdvisorCommented:
yes.  Choose the source same as destination just change the name for it so it doesn't conflict with the current VM.  Do the V2V and do not power up the new VM until you make sure the first one is offline (you can do it online or offline depending whether you need it to stay up and whether the data changes)  If doing online point to the OS, if doing offline point to the VM in vCenter/ESX/ESXi
reredokIT ConsultantAuthor Commented:
After waiting hours ... ;-) no change :-((

Inside a experimental VM with same -delta Problem, I establish a new Snapshot. New big Files were created:
W3KTS02-000004-delta.vmdk ...

Then I've shutdown VM and after getting some curious errors in VMware Infrastructure-Client, I wasn't able to start VM until this morning.
So restart is complete and *magic* all -delta-File were deleted :-)

Actually I'll test this concept on other problem-vm's
If the virtual machine isn't running when you are deleting snapshots then the process will be quicker as ESX doesn't have to cope with handling new changes whilst commiting/deleting old changes.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.