VMware Cloud Community
andi303
Contributor
Contributor

Problem shutting down VM after creating backup task

Hello all,

I can't shut shut down one of my VMs after creating a backup job.

The backup of this specific VM fails when creating the snapshot (well, it's not a disc space issue). Now I can't shut down the VM! The vSphere Client always says that the VM is already executing another task. I've already excluded the VM from the backup task without success.

I can't even shutdown the ESXi host, because the VM is still turned on...

Is there anything I can do to solve this problem?

Thanks in advance,

Andreas

Reply
0 Kudos
7 Replies
AndreTheGiant
Immortal
Immortal

In which way are you shutting down the VM, using VIC, using CLI, ..?

And why are you making a snap before shutdown?

The sequence for scripted backup without agent or VCB could be: shutdown guest, snap, power-on, backup, remove snap.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
andi303
Contributor
Contributor

The Backup is done via VMWare Data Recovery.

I'm just trying to shut down the VM indepently from the backup job. I'm using the vSphere Client.

Andreas

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

But the backup is finished when you tried to shutdown?

Are you using guest shutdown?

Inside the VM are you able to launch the shutdown operation?

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
dtracey
Expert
Expert

Hi Andreas,

Have you tried running the following commands from the ESXi console?

vmware-cmd vmfs/volume/vmfslabel/VMName/VMName.vmx stop trysoft

or

vmware-cmd vmfs/volume/vmfslabel/VMName/VMName.vmx stop hard

?

Let us know.

Dan

andi303
Contributor
Contributor

But the backup is finished when you tried to shutdown?

NO, the backup job says that the snapshot can't be created.

Are you using guest shutdown?

Yes

Inside the VM are you able to launch the shutdown operation?

Yes, but the vSphere Client still lists the VM as powered on. When I open a console, I get the following message:

"Unable to connect to the MKS: There is no process running for config file /vmfs/volumes/4a2f56f2-85061650-6ceee-00137254f469/chs/chs.vmx.

Reply
0 Kudos
andi303
Contributor
Contributor

Dan,

same problem here. The SOAP response says "TaskInProgress".

Reply
0 Kudos
andi303
Contributor
Contributor

OK, Restarting the whole ESXi host from the direct console worked. The host restarted with the VM in "turned off" state.

I've planed a new backup task for the VM, I hope it'll work this time. I'll get the results tomorrow.

Again, thanks for your help!

Reply
0 Kudos