Home > Virtualization > Slow Exporting OVF/OVA from vSphere Client or ovftool? A Quick Tip Can Save You Hours

Slow Exporting OVF/OVA from vSphere Client or ovftool? A Quick Tip Can Save You Hours

November 8th, 2016 Leave a comment Go to comments

Over the weekend, I was trying to export a virtual machine from vSphere using ovftool command line. To my surprise, it was extremely slow. In fact, I wasn’t patient enough to wait for its finish and “Contrl+C” it. Initially I was thinking it could be ovftool issue, so I tried exporting from vSphere Client directly. Still very slow and I had to cancel it as it would run for a few hours according to the progress dialog box.

To root cause the problem, I tried:

Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.

  1. Restart the vCenter vpxd service
  2. Reboot vCenter server
  3. Connect vSphere Client directly to the ESXi server
  4. Reboot ESXi

Nothing changed – still extremely slow.

I had similar virtual machine exported consistently within 10 minutes before. The virtual machine is configured with two disks, one of which is pretty small and the other is 1TB. Both virtual disks are thin provisioned. When successfully exported as before, the OVA file size should be 800MB or less.

As I posted a question on the vExpert forum, I got helps from Steve Kaplan who thought it’s a VM related issue. It reminded me to go on another test: deploy the previously exported OVA to a VM, and export it again to OVA. The magic happened – the export was done in 10 minutes.

Now, what is the difference of the my current VM and the newly deployed? After comparing the datastore folders of both VMs, I found that my current VM has a snapshot and the newly deployed does not. It then started to make sense: when a virtual disk has a snapshot, it will have to first combine the original disk and snapshot delta disk into current one. Regardless the thin provisioned format, the combination process may have been done as if it were normal disk. In my case, the exporting of the VM is like exporting a thick provisioned 1TB VM.

So I decided to consolidate the virtual disks and see whether it could make any difference. Luckily, it worked.

The key takeaway from reading this post is:

MAKE SURE NO SNAPSHOT when exporting a VM regardless it’s thin provisioned.

 

Categories: Virtualization Tags:
  1. November 8th, 2016 at 00:01 | #1

    [DoubleCloud] Slow Exporting OVF/OVA from vSphere Client or ovftool? A Quick Tip Can Save You Hours https://t.co/7Of7cjxoRu

  2. November 8th, 2016 at 03:51 | #2

    Slow Exporting OVF/OVA from vSphere Client or ovftool? A Quick Tip Can Save You… https://t.co/MYcYW4SDzG #Virtualization #4767444837072896

  3. November 9th, 2016 at 08:46 | #3

    Useful information. Lucky me I found your site accidentally, and I am
    shocked why this twist of fate didn’t happened in advance!
    I bookmarked it.

  4. November 15th, 2016 at 20:06 | #4

    For most up-to-date information you have to visit world-wide-web and on internet I
    found this site as a most excellent website for newest updates.

  5. November 22nd, 2016 at 11:56 | #5

    If you would liike to increase your knowledge just keep
    visiting this web site and be updated wifh thhe newest information posted
    here.

  1. No trackbacks yet.