Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

A guest on VMWare ESXi 4 is not booting anymore and I want to attach its disk to another machine. Both are almost identical ubuntu 64 bit server instances.

But the broken machine had snapshots, so vSphere client offers me to add from 2 vmdk files:

  • redmine-alt-clon.vmdk 4GB
  • redmine-alt-clon-000003.vmdk 257MB

This is a screenshot of the situation on the harddrive:

enter image description here

So is it fine to just add the first one that vSphere finds (redmine-alt-clon.vmdk) and I get the drive contents from yesterday?

(This would mean the other small file with -000003 and the delta file contains the old state or the difference makes the old state that I no longer need.)

Or if it is not that simple, what can I do to get yesterdays state of the drive without starting the vm or reverting the snapshot.

I would rather avoid reverting the snapshot from vSphere client because the broken vm is no longer available with all files.


EDIT: What I found out after some time is that more delta files like 00002-delta are missing (the parents, as there were more snapshots in the chain) and so it was not possible to fix the issue for me. But the different answers below should help in similar cases if all necessary snapshot files do still exist (and they should normally).

share|improve this question
add comment

3 Answers 3

up vote 2 down vote accepted

A snapshot is a delta of the hd from N until NOW, where N is when the snapshot was actively "taken." So, this looks like the -00003-delta contains the info that was changed since the beginning of the snapshot. My suggestion, make a back up. You can even copy these suckers down to a workstation and use VMWare or VirtualBox to mess around

What do you "bad news?" Just copy all those files down, and you'll have a full vmdk with a snapshot. The info files should contain information about the snapshots etc.

share|improve this answer
    
Thank you. I understand now better. –  mit Oct 12 '11 at 10:17
    
More importantly... did it work? –  mbrownnyc Oct 12 '11 at 17:23
    
What I found out is that more delta files like 00002-delta are missing (the parents, as there were more snapshots in the chain) and so it was not possible. But your answer is correct and helped to understand –  mit Oct 15 '11 at 12:26
    
That's too bad man. Well, better luck next time! Hopefully you have good backups of that server itself, or at least the data on it, so that you can role out a new instance pretty quickly. Good luck! –  mbrownnyc Oct 15 '11 at 17:17
add comment

Well in my opinion you should clone that disks before you copy.

When cloning that disks will remove any snapshots and you will have only the VMDK form the disks.

This tasks is performed by using the command vmkfstools

Check VMware article how to clone that disks and understand how it works. Read the article to understand the snapshots and also the check the video to learn how to perform this task.

http://kb.vmware.com/kb/1007849

This will consolidate the snapshots and also create a clone/copy of that disks. Then you can just copy this clone to other VM and used.

Hope this can help

share|improve this answer
add comment

Just had similar issue, this two VMware KB articles came with help.

Recreating a missing virtual machine disk (VMDK) descriptor file: http://kb.vmware.com/kb/1002511

Recreating a missing virtual disk (VMDK) descriptor file for delta disks: http://kb.vmware.com/kb/1026353

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.