VMWare 4.1 VM is hanging on shutdown/snapshot removal

I have a VM that is stuck trying to delete a snapshot & then shutdown. It has been sitting on 95% for over an hour.

Does anyone know how I can force this VM to shutdown? The buttons to shutdown are greyed out.
someITGuyAsked:
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.

coolsport00Commented:
How big is the snapshot? Depending on its size, it could take well longer than an hour...

~coolsport00
0
someITGuyAuthor Commented:
It was progressing over 2 hours, just in the last hour it is hanging on 95% and not moving...
0
coolsport00Commented:
How big is the snap (or snaps)?
0
Ultimate Tool Kit for Technology Solution Provider

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 now.

someITGuyAuthor Commented:
Not sure, how do I check?
0
coolsport00Commented:
You can go into the folder of the VM on the datastore and look at the 'delta' files to see their size. A couple things to note:
a. It's best practice to always shut down a VM before you remove its snaps. You don't have to, but tends to run a bit smoother.
b. See this post on snapshot 'committing' looking like it's hanging on 95%:
http://blog.frode.org/?p=31

There is a way to monitor the 'commit' process in the cmd line:
http://kb.vmware.com/kb/1007566, but it may be more than you wanna tackle at this point. If you've had this VM 'snapshotted' for a while, chances are the snap (delta) file is a bit large (many GBs). If that's the case, expect this commit process to take several hours.

Thought I'd also post a couple other KBs worth looking at:
Understanding Snaps:
http://kb.vmware.com/kb/1015180
Snap Best Practices:
http://kb.vmware.com/kb/1025279

Regards,
~coolsport00
0

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
BWaringCommented:
I've had it take several hours.... depends on several factors, with the size of the snapshot being first... if you browse the datastore you can see how big it is...
0
coolsport00Commented:
Another option you could use, if you're not comfortable committing them with the Client/snapshot mgr is to just clone the VM or use vCenter Converter. Using those processes commits the snaps during the conversion and/or clone process. Always try not to have snaps a part of a VM more than a day or 2, at most...

~coolsport00
0
someITGuyAuthor Commented:
I just rebooted the VCenter server & it looks like the snapshot hang went away...
0
coolsport00Commented:
I never would recommend doing that during a vCenter process, beit snapshot commit or whatever. It will end on its own. You can corrupt your VM interrupting a snap commit process. You can verify that the snaps are gone by looking the VM's folder on the datastore and verifying if the snap (delta) files are gone. If the commit process wasn't yet complete, you could be back to square 1 with all the data still in the snap and new data getting written to the snap file until it's actually committed to the parent disk. Also, you may now not have the option in snapshot mgr to 'see' the snaps, and thus commit them. If not, you will have to use command  line to do so. See:
http://kb.vmware.com/kb/1002310, and
http://kb.vmware.com/kb/1006847

~coolsport00
0
BWaringCommented:
Was about to type the same thing!
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Normal for it to sit there at 95%, until it has completed. (as the fellow Experts have made comments on!)

It must have been a very large snapshot. Again do not use Snapshots for Backup purposes.
0
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
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.