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

  • VMware Workstation updated to 9.0.2

    VMware
    0 Comments

    VMware is released a maintenance update for VMware Workstation to version 9.0.2. The update is available for free for all VMware Workstation 9.x customers.

    Mostly just bug fixes and a few improvements, here are a few highlights:

    • Fedora 18 supported as a guest operating system
    • Windows 8 host permissions issues fixed
    • VMware Tool updated to support the latest Linux kernels
    • Improved general host resource management
    • OVF Tool has been updated to version 3.0.2
    • Virtual machine sharing improvements
    • Memory leak which impacted Windows hosts has been fixed

    Read More “VMware Workstation updated to 9.0.2”

  • VMUG EVALExperience, the new VMware VMTN

    VMware
    0 Comments

    VMUG EVALExperience

    Long ago VMware offered a program called VMware Technology Network (VMTN) which was very similar to Microsoft’s TechNet, which allowed you to download and run various VMware software within your home lab for a small yearly fee. Just like the Microsoft TechNet, the VMware VMTN program was eventually closed. From the time the VMTN program closed many people have begged and pleaded with VMware to bring the program back, there is even a long forum thread asking VMware to bring VMTN back. Though it never did… until now.

    Read More “VMUG EVALExperience, the new VMware VMTN”

  • VMware Recertification Policy

    VMware
    1 Comment

    VMware certified

    Starting today, March 10 2014, new VCP certifications must be re-certified within two years of it’s earned date. Anyone who currently has their VCP certification prior to March 10 2013 has until March 10, 2015 to re-certify.

    The new policy gives you three options to re-certify:

    1. Take the current exam for your existing VCP certification solution track. For example, if you are a VCP3, you could take the current VCP5-Data Center Virtualization (VCP5-DCV) exam.
    2. Earn a new VCP certification in a different solution track. For example, if you are a VCP-Cloud, you could recertify by earning VCP5-Desktop (VCP5-DT) certification.
    3. Advance to the next level by earning a VMware Certified Advanced Professional (VCAP) certification. For example, if you are a VCP5-DCV you could earn VCAP5-DCA certification.

    I can understand why they are doing this but I don’t agree with the changes. As per the announcement if you let your certification expire, “Your certification will be revoked,and you will no longer be entitled to use the certification logo or represent yourself as VMware certified“. Really? You mean everything that was done prior and after taking the exam means nothing?

    Read More “VMware Recertification Policy”

  • VMware Workstation 12 Pro Released

    VMware
    0 Comments

    VMware has just released a new version of Workstation in VMware Workstation 12 Pro. Workstation 12 Pro provides full support for Windows 10, including features such as Cortana and universal applications. As well as even larger virtual machines with up to 16 vCPU’s and 64GB of memory. Workstation 12 Pro even supports 4K displays and DirectX 10 and OpenGL 3.3

    You can even seamlessly drag and drop virtual machines between your PC and your internal cloud running vSphere, ESXi or another instance of Workstation. In addition, easily connect to vCloud Air and upload, run, and view virtual machines right from the Workstation 12 Pro interface.

    Read More “VMware Workstation 12 Pro Released”

  • Upgrade vCenter Server Appliance 6.0 to 6.5

    VMware
    27 Comments

    VMware vSphere 6.5 has been released as general available and earlier this week I posted about Installing VMware vCenter Server Appliance 6.5 as a new install, this post will walk through upgrading an existing vCenter Server Appliance 6.0 to 6.5!

    Similar to a fresh VCSA 6.5 install, the VCSA 6.5 upgrade is also broken up into two stages. The first stage is deploying a new vCenter Server Appliance and the second stage is copying data from the 6.0 VCSA to the newly deployed 6.5 VCSA.

    Read More “Upgrade vCenter Server Appliance 6.0 to 6.5”

Leave a Reply to Ganesh Misal Cancel 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