VMware Cloud Community
rinkals
Contributor
Contributor

esxi 5.5 snapshot greyed out for one vm

Hi,

I have 4 vm's running on one host, 2 running windows and 2 running redhat linux

I am able to snapshot all the vm's apart from 1 of the redhat.

I have tried and checked the following:

1. Permissions of the VM (same as the rest which are working)

2. Restarted management agents from esxi console

3. Checked the vmx file for blank lines / corruption none found

4. Reloaded / created the vmid from the console

5. Checked for running tasks (none found)

6. Restarted guest OS All OK

7. Restarted Esxi Host All OK

Still unable to perform snapshot.

I am pretty new to vmware / esxi so not sure what to look for next or if there is more to check in the steps I have done?

Ultimate goal is to use veeam which ir working fine on the other 3 vm's.  Veeam say must be able to do snapshot before they will assist.

Thanks in advance.

Tags (1)
0 Kudos
4 Replies
npadmani
Virtuoso
Virtuoso

What's the exact error message when you try to take snapshot of that VM?

Narendra Padmani VCIX6-DCV | VCIX7-CMA | VCI | TOGAF 9 Certified
0 Kudos
continuum
Immortal
Immortal

There are quite a few vmx-paramers that could prevent a snapshot - some of them are obvious - some are not.

A vmware.log that includes a failed attempt to creater a snapshot would surely help now.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
a_p_
Leadership
Leadership

I agree with continuum, the VM's vmware.log should help finding out what's going on. Either check it yourself, or attach it to a reply post.

On thing that I could think of is that the VMware Tools installation is still in progress, i.e. didn't complete properly!?

André

0 Kudos
FritzBrause
Enthusiast
Enthusiast

Shut down the VM.

Create a new VM with same settings.

Copy over the .vmdk file into the new VMs home folder (using Datastore Browser or vmkfstools -i in the console).

(Of course you can also use the existing .vmdk file, but then you have a new VM folder pointing to the old folder; just cosmetic).

See if snapshots are working with the new VM.

If everything is fine, delete the old VM.

0 Kudos