VMware Cloud Community
JHartwig
Contributor
Contributor
Jump to solution

ESX - problems with snapshots

Hi,

Recently we had som issues with our ESX 4. We solved the main issue that was how to recover the esxconsole.vmdk. We used this KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101287...http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101287... and http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100251....

However one of the virtual machines couldn´t start. I solved that issue using the KB1002511 (sea above). Now it start fine however it starts as it where 13th december 2011, that was before i made the first snapshot.

In my datastore1 I have these files for my virtual machine Wiki:

-rw-r--r-- 1 root root 66221 Feb 25 02:36 vmware.log
-rw------- 1 root root 67133440 Dec 14 00:54 Wiki-000001-delta.vmdk
-rw------- 1 root root 1694523392 Dec 15 17:47 Wiki-000002-delta.vmdk
-rw------- 1 root root 637558784 Dec 24 14:31 Wiki-000003-delta.vmdk
-rw------- 1 root root 704667648 Feb 21 09:38 Wiki-000004-delta.vmdk
-rw------- 1 root root 10737418240 Feb 25 02:36 Wiki-flat.vmdk
-rw------- 1 root root 8684 Feb 25 02:36 Wiki.nvram
-rw------- 1 root root 465 Feb 25 00:32 Wiki.vmdk
-rw-r--r-- 1 root root 0 Feb 25 02:15 Wiki.vmsd
-rwxr-xr-x 1 root root 2603 Feb 25 02:36 Wiki.vmx
-rw-r--r-- 1 root root 259 Feb 25 02:15 Wiki.vmxf


Is it possible to put my VM back at it was the 21th Februari? I´ve tried using this KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100231... but haven´t succeded!

The VM is a Wiki (MediaWiki), using Centos 5, 64-bit version.

Please help me out.

Kind Regards

Johnny

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

It looks like you lost the descriptor files for the snapshots and attached the base disk to the VM, which caused the "loss" of current data. Since you powered on the VM with the base disk attached to it, there might be some data corruption in the file system, although I think this should be minor due to the snapshot sizes. I created a set of files based on the .vmdk file's time stamps which should repair the snapshot chain and run the VM from snapshot 4.

Please follow these steps:

  1. power off the VM (actually I hope it's still powered off)
  2. remove the VM from the inventory (right click the VM)
  3. upload the files from the attached .zip file to the VM's folder on the datastore
  4. add the VM to the inventory (right click the .vmx file)
  5. create a new snapshot!
  6. power on the VM

André

View solution in original post

0 Kudos
8 Replies
a_p_
Leadership
Leadership
Jump to solution

Welcome to the Community,

as a first step, power off the VM immediately if not already done.

Then reply here and attach a .zip archive with the latest vmware.log from theVM's folder as well as all the .vmdk header/descriptor files (you will need to download them using e.g. WinSCP)

André

0 Kudos
JHartwig
Contributor
Contributor
Jump to solution

I´ve downloaded the  vmware.log and wiki.vmdk among some other. Would you like the large vmdk as the -flat.vmdk and the -delta.vmdk as well?

Thank you for your reply!

/Johnny

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

It looks like you lost the descriptor files for the snapshots and attached the base disk to the VM, which caused the "loss" of current data. Since you powered on the VM with the base disk attached to it, there might be some data corruption in the file system, although I think this should be minor due to the snapshot sizes. I created a set of files based on the .vmdk file's time stamps which should repair the snapshot chain and run the VM from snapshot 4.

Please follow these steps:

  1. power off the VM (actually I hope it's still powered off)
  2. remove the VM from the inventory (right click the VM)
  3. upload the files from the attached .zip file to the VM's folder on the datastore
  4. add the VM to the inventory (right click the .vmx file)
  5. create a new snapshot!
  6. power on the VM

André

0 Kudos
JHartwig
Contributor
Contributor
Jump to solution

Thank you André! You made my day, possibly even my month! 😉

I did as you said. All worked immediately!

Can you explain how you solved the issue?

Best Regards,

Johnny

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

You are welcome and thanks for the feedback.

Once you have verified that everything works as expected, I'd recommend you delete the snapshot (unless you need them for any reason). To do this run "Delete All" from the Snapshot Manager.

André

a_p_
Leadership
Leadership
Jump to solution

Can you explain how you solved the issue?

It was actually quite easy. First I verified the disk size and geometry for the Wiki.vmdk, based on the flat file's size (http://forums.phdvirtual.com/wrapgen/), then I created the descriptor files for the snapshots, also based on these values. Snapshots in VMware products work like a chain, one is based on the other (http://kb.vmware.com/kb/1015180), so I just needed to configure unique values for CID as well as parentCID and chain the snapshots in the correct order (based on their time stamps). Last step was to set the latest snapshot as the active virtual disk in the configuration (.vmx) file.

André

fletch00
Enthusiast
Enthusiast
Jump to solution

I'm about to try KB 1002511 on ESXi 5.5

The small header vmdk got deleted.

This VM has 1 snapshot - what is the trick to linking the snapshot back up?  I don't think its in KB 1002511

thanks!

VCP5 VSP5 VTSP5 vExpert http://vmadmin.info
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Please consider to open a new discussion and provide the required information, i.e. a complete list of files (the output of ls -lisa from the command line), and - unless all descriptor .vmdk files got lost - attach the remaining .vmdk file(s) as well as the VM's .vmx file to a reply post.

André

0 Kudos