VMWare ESXi 4.1 - Accidentally deleted config files

In the process of cleaning up a VMWare 4.1 all the configuration files for a running Virtual Server were deleted.  The actual hard disk files were not deleted because they were in use.  I thought I could just shut down the system and build a new VM and choose to add the Hard Disks that were previously created.  I shut down the VM and created a new Virtual Machine but when I go to add the Hard Drives the files are not listed.  I can see the files when I browse the DataStore.  It looks like there was a snapshot that had been created.  I have the following files...

Caroline-XXXXXX.vswp
Caroline-flat.vmdk
Caroline-000001-delta.vmdk

The delta file has today's date.

Please help.

Thanks,
John
LiberatingInsightAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Now that you have started the VM on the parent disk, without the snapshot attached, you will now have to fix the mismatching CIDs!

see here

VMware KB: Resolving the CID mismatch error: The parent virtual ...

once you have done this, the best think would then create a new virtual disk, using the clone technique

vmkfstools -i <most recent snapshot file name> /vmfs/volumes/<temp folder name>/<newfilename.vmdk>

and then newfilename.vmdk is your new virtual machine disk to attach to your VM.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
can you check you have just two VMDKs?

you may need to do this via SSH?

you should have

Caroline-flat.vmdk
Caroline.vmdk
Caroline-000001-delta.vmdk

do you have Caroline.vmdk ?

also screenshot would be good?

It looks like you are missing the descriptor file?

this can be re-created?

Recreating a missing virtual machine disk (VMDK) descriptor file
0
 
LiberatingInsightAuthor Commented:
I do not have the Caroline.vmdk file.  Here is a screenshot of browsing the datastore.


I'm going to try the recreating the VMDK descriptor file.  Is there any special concerns since there is a Snapshot?
Screen-Shot-2014-01-08-at-11.52..png
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
The descriptor has been deleted.

Create the descriptor as normal.

and then add the snapshot delta disk, because it chains the parent, or I could show you how to clone the disk, so you have a single parent disk.
0
 
LiberatingInsightAuthor Commented:
I created the descriptor files for both the main and the snapshot vmdk's.  When I attempt to add the disks to the new Virtual Machine I get an error:
An internal error occurred in the vSphere Client.
Details: Object reference not set to an instance of an object.

I ran the vmkfstools -q on both files and they both came back with "... is not an rdm" which I think means both disks are good.

Not sure where to go.

I was able to mount the Caroline.vmdk drive and booted the VM and it came up and started windows but I need the Snapshot data.
0
 
LiberatingInsightAuthor Commented:
Cloning the disk fixed it.  Thank you VERY MUCH!!!
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
No Problems...Glad to help!
0
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.

All Courses

From novice to tech pro — start learning today.