VMware Cloud Community
Tashi
Contributor
Contributor
Jump to solution

Can`t commit Snapshots

Hi all

On one VM we can`t commit the Snapshots. I also tried to create a new Snapshot (this works) and then delete all Snapshots (as suggested by other treads). This can be done. But the Snapshots are not deleted. For everytime I try this, I get another delta file.

Here are the listed vmdk files from the directory.

clo2_VM_161522544_1-000001-delta.vmdk

clo2_VM_161522544_1-000001.vmdk

clo2_VM_161522544_1-000002-delta.vmdk

clo2_VM_161522544_1-000002.vmdk

clo2_VM_161522544_1-000003-delta.vmdk

clo2_VM_161522544_1-000003.vmdk

clo2_VM_161522544_1-000004-delta.vmdk

clo2_VM_161522544_1-000004.vmdk

clo2_VM_161522544_1-000005-delta.vmdk

clo2_VM_161522544_1-000005.vmdk

clo2_VM_161522544_1-000006-delta.vmdk

clo2_VM_161522544_1-000006.vmdk

clo2_VM_161522544_1-flat.vmdk

clo2_VM_161522544_1.vmdk

clo2_VM_161522544-flat.vmdk

I don`t know why I have no delta file from the first disk. In the Edit Settings Windows I also see the first Diskfile is mapped to a -00000.vmdk file.

This happed because a script accidentally shutdown the system while we clone it.

Any help would be really appreciate.

Tashi

Reply
0 Kudos
1 Solution

Accepted Solutions
RParker
Immortal
Immortal
Jump to solution

Forget playing with the vmx file and manipulating settings. Set the snapshot to the correct (or latest) version of the VM.

Power it OFF.

Rename it to something like vm-name-backup

CLONE it as a NEW VM with the same original name.

Done. Much easier than trying to FIX the issue. If ALL you want to do is simply get rid of ALL the snapshots, this is the BEST method for this. Make sure you delete the original VM folder when done.

View solution in original post

Reply
0 Kudos
5 Replies
a_p_
Leadership
Leadership
Jump to solution

Tashi,

please post a complete list of files showing the names, sizes and time stamps. Also attach the clo2_VM_161522544.vmx file.

André

Reply
0 Kudos
kjb007
Immortal
Immortal
Jump to solution

Does the system still power on? If it does, and you have the space, I'd run converter against it and get a working clone of the system. Working with large snapshot trees can get confusing.

Also, make sure the datastore location for the original drive is where you expect it to be by looking at the full locaiton in the drive properties.

vExpert

VMware Communities Moderator

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
RParker
Immortal
Immortal
Jump to solution

Forget playing with the vmx file and manipulating settings. Set the snapshot to the correct (or latest) version of the VM.

Power it OFF.

Rename it to something like vm-name-backup

CLONE it as a NEW VM with the same original name.

Done. Much easier than trying to FIX the issue. If ALL you want to do is simply get rid of ALL the snapshots, this is the BEST method for this. Make sure you delete the original VM folder when done.

Reply
0 Kudos
MauroBonder
VMware Employee
VMware Employee
Jump to solution

have this kb, maybe helpful - Consolidating Snapshots http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100784...

*If you found this information useful, please consider awarding points for "Correct" or "Helpful"*

*Please, don't forget the awarding points for "helpful" and/or "correct" answers. *Por favor, não esqueça de atribuir os pontos se a resposta foi útil ou resolveu o problema.* Thank you/Obrigado
Tashi
Contributor
Contributor
Jump to solution

Great! Thank you all! My Problem is solved. Sorry for the late response.

I cloned the System. Now all Snapshots are Consolidated :smileygrin:

Reply
0 Kudos