Restore a VM using the {vm}-flat.vmdk file

VMware

missing vmdk file error

A couple days ago I was asked the question “An admin deleted the vmdk file associated with a VM, there are no snapshots or backups of the VM . Can we restore this VM somehow?“. I believe in backups, I like to have my VM’s backed up so that I can depend on them for events just like this very issue. At first I was stumped, until the {vm-name}.flat.vmdk was mentioned. That’s when I remembered a method to recover a VM using the vm-flat.vmdk file that I had actually done 2-3 years ago.

Example preparation

For this example I’ve created a Server 2012 virtual machine (called Win2012) and placed a text file on the desktop called “Important Info”. I then deleted all the files associated with that VM with the exception of the Win2012-flat.vmdk file, as seen in the image at top.

VM before deleting VMDK file

After the files had been deleted I tried to power up the VM knowing it would not and received this error.
missing vmdk file error

Ok, now on to how to restore a VM with a missing .VMDK file.

How to Recover a VM using a vm-flat.vmdk file

  1. I created a new VM called Recovery with the same specs as my Win2012 server (2vCPU, 4GB RAM, 40GB HHD).
  2. Enable SSH on the host and logged in via PuTTy (or WinSCP) and verified the contents of Win2012 folder: 
    cd /vmfs/volumes/vmNFS02/Win2012/

    win2012 folder contents

  3. Then navigate to the Recovery VM folder. 
    cd ../Recovery/
  4. Rename the original Recovery-flat.vmdk file to Recovery-flat.vmdk.bak 
    mv Recovery-flat.vmdk Recovery-flat.vmdk.bak

    copy recovery-flat.vmdk

  5. Now just copy the Win2012-flat.vmdk file from the Win2012 folder over to the Recovery folder (Note: This step could take several minutes): 
    cp /vmfs/volumes/vmNFS02/Win2012/Win2012-flat.vmdk Recovery-flat.vmdk

    copy flat vmdk to recovery folder

  6. Finally, power up the new Recovery VM and your old VM (Win2012) should be back online good as new!
    after restore
  7. You can also go back and delete the Recovery-flat.vmdk.bak file as it won’t be needed.

So even though restoring a VM from a -flat.vmdk file is pretty easy it isn’t my recommended method, you’re far better protected with good, reliable backups, then on hoping that the -flat.vmdk file is still laying around somewhere.

Similar Posts

How to run Crashplan in Docker on Synology NAS

Synology
147 Comments

Crashplan running in Docker on Synology

I am a huge fan of CrashPlan and have been using it for years on my Synology NAS using this install guide I wrote up some time ago.

Admittedly the process in the old guide wasn’t always roses. Crashplan would push out an update and that update would, at times, break the Synology Crashplan client from PC Load Letter and backups would stop running for a couple days – maybe a week. Patters being the awesome guy he is, usually updated his Synology Crashplan package quickly and all was good again.

Then last year in DSM 5.2, Synology added support for Docker which opened up the possibility to run all sorts of software in a virtual container running on your Synology NAS. One such software being Crashplan and below I’m going to show how I now have Crashplan running in Docker on my Synology DS1815+ NAS!

Read More “How to run Crashplan in Docker on Synology NAS”

vSphere 5.5 Update 1 has been released, includes VSAN.

VMware
1 Comment

VMware vSphere 5.5 update 1

VMware has officially released vSphere 5.5 U1 which includes a number of improvements, fixes, and most excitedly the production ready version of VSAN!

What’s new

  • vCloud Hybrid Service vSphere Client Plug-in, is now available in vSphere Web Client.
  • vCenter Server is now supported on Windows Server 2012 R2.
  • A number of resolved issues

Read More “vSphere 5.5 Update 1 has been released, includes VSAN.”

Fix VMware VCSA /storage/log filesystem out of disk space

VMware
14 Comments

This morning I ran into an issue where users were reporting the production VCSA 6.0 was not allowing them to connect into the web or thick client. Another administrator rebooted the VCSA which seemed to work only briefly. I then logged into the VCSA web management (https://<VCENTER_IP>:5480) and noticed the following health status right away:

The /storage/log filesystem is out of disk space or inodes

vcsa /storage/log full

Read More “Fix VMware VCSA /storage/log filesystem out of disk space”

How to upgrade ESXi 6.5 to ESXi 6.7

VMware
10 Comments

VMware released ESXi 6.7 a little while ago, but it’s only been here recently have I started deploying it in my home and work lab environments. Below are two ways to easily upgrade your ESXi 6.5 hosts to ESXi 6.7 using the command line or by using the VMware ESXi offline bundle.

Read More “How to upgrade ESXi 6.5 to ESXi 6.7”

How to fix vRealize Orchestrator 6 appliance, weak ephemeral Diffie-Hellman key

VMware
0 Comments

vrealize orchestrator chrome error

I’ve recently deployed the vRealize Orchestrator appliance (6.0.2) and noticed right away that my default browser Firefox, would not load the Orchestrator appliance web panel. Firefox always complained about a weak Diffie-Hellman key.

“An error occurred during a connection to ip-address:8281. SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. (Error code: ssl_error_weak_server_ephemeral_dh_key)”

At the time I simply ignored it and just tried Google Chrome which it worked fine. That was until the latest release also broke with the same type of error message:

“Server has a weak ephemeral Diffie-Hellman public key“.

I now had a problem and contacted VMware support, below is the very easy fix to make vCO 6 work in both the latest version of Firefox and Chrome!

Read More “How to fix vRealize Orchestrator 6 appliance, weak ephemeral Diffie-Hellman key”

Leave a Reply

Your email address will not be published. Required fields are marked *

34 Comments

  2. Hi,

    Thanks for the above post :)

    I’m try your post in my home lab but I’m facing the below
    issue . can you please help me to understand the concept .

    I have created a new VM called win7 then logged into the ESXi 5.0 via SSH (putty ) I can view the win7-flat.vmdk
    file but if I delete the win7.vmdk file I can’t see the win7-flat.vmdk . because
    of this I’m not able to perform your post in my lab can you please help me understand
    the concept please and please guide me if I’m wrong

    Reply

    1. viswa,

      How are you deleting the .VMDK file? If
      removing the VM from disk it will in fact remove all files and folder
      associated with the VM. If you’re browsing the VM folder on the
      datastore and delete the .VMDK file then the {vm}-flat.vmdk file should
      still exist.

      Reply

      1. Hi Michael,

        Thanks for your help :)

        How are you deleting the .VMDK file?
        Ans : I’m browsing the VM folder in data store and deleted the
        win7.vmdk file . after that i’ve checked ssh to ESXi via putty i’m not able to view the both Vmdk and flat.vmdk files

      2. viswa,

        Sounds like you’re deleting it from the GUI datastore browser. I deleted the file from SSH. Not sure if that might be the issue or not, but i will try it when I get home this evening on my home lab as well.

        If you want to test now you could spin up a new test VM, SSH to the VM folder and delete everything but the {vm}-flat.vmdk file and try the rest of the steps.

  3. Pingback: Restore a VM using the {vm}-flat.vmdk file | Iron Castle Systems

  4. Hi i have this problem in real VM , i do these note but my machine isn’t work.
    i work with gui datastore browser.plz help me :(

    Reply

  5. Thank you very must you saved me, after the material virtual update 9 to 10, the DIsk 1 size take 0 MB (usual 50 GB)
    In a friday (newer do a action on prod a friday ! -but the deadline – grrrrr)

    Imagine I give a virtual Beer ;-) sluurps :)

    From France.

    Reply

  6. This worked like a charm! Thanks a million! This was a life saver. I was able to recover my Lync 2013 Server with no issues using these instructions. Straight forward and clear.

    Reply

  7. Hi Mike, do you have an article I can use to get my Datastore (from Synology iSCSI Target) to show up on my VMware host again? I am able to connected successfully and see it mounted but I no longer see the Datastore from Synology showing up on my ESXi Hosts. Thanks!

    Reply

    1. Hector,

      I don’t have an article for mounting iSCSI targets from Synology to VMware but wouldn’t mind creating one. If you’ve already had this configured at one time then it makes me wonder what has changed since? Also have you tried to do a storage rescan?

      -Michael

      Reply

  8. hi mike, iam download vm files from one datastore to another data store, I notice that i click download from datastore on my local drive, file is downloading but file name appears on my local drive is myvm-flat.vmdk, why the flat added in it? how can i send you private message or skype? i want to share my screen shots with you

    Reply

  10. Thank you, thank you, thank you
    You saved my server, did not have any current backups because it was temporary, but SAP consultants never released it.
    Great job and article

    Reply

  13. How do you find the location of the VM to type it in the “cd /vmfs/volumes/vmNFS02/Win2012” command?

    I am pretty new at this and somehow my vm server had a “bootstrap device not found” error, things got complicated from there — I tried recreating the VM and using the disks of the bad VM, but that gave me another error (bootmgr not found) and even then after using chkdsk tools it went worse.

    I do have the flat.vmdk file for the original VM but nothing else – it seems it is the right size.

    I am not sure how to find the location of that to type in the above command. PLEASE, help!

    Thanks a lot.

    Reply

  16. Ref: Hi mike, Im download vm files from one datastore to another data store, I notice that i click download from datastore on my local drive, file is downloading but file name appears on my local drive is (myvm-flat.vmdk) this is a backup file from in esxi virtual harddisk

    Another way to save te info when we get a -flat.vmdk file, is with power iso, this app can open te file .vmdk as it was a .rar file and extract the needed files and folders.

    Thanks to you and and other soulds that saved my day and night and 3years of works!

    Reply