• Preetam Zare

Migrate from any hypervisor to any hypervisor using vembu

We can use Vembu to migrate VMs to any hypervisor. Such tools are available in the market, but what is unique about Vembu it offers this feature as a part of the backup suite. I can backup VM in VMDK (VMWare) format and restore it to hyper-v format. This Feature can of great use if you are using different hypervisor in DR than in production. Let me describe the use case.

Use Case: Migrate from VMware to Hyper-V, VMware to KVM, Hyper-V to VMware, Hyper-V to KVM, KVM to Hyper-V, KVM to VMware  (Any to Any Hypervisor)

I’m running VMware in Production. I want to migrate to Hyper-V. Hyper-V is running in Destination site. As a first step, I will install and configure vBDR to backup all VMs. While my goal is to move them to Hyper-V which is running in destination site, I need storage. I used migration hardware, installed Windows 2012 R2 and installed the iSCSI feature on the server. In vBDR which is also running Windows 2012 R2, I configured it iSCSI initiator. During the weekend I used a restore option to download all VMs as VHDX format. I carried the hardware to the destination site, install iSCSI initiator on Hyper-V. Since I have previously configured Migration hardware as Target, nothing was needed. At destination site, I created VMs and attached new VHDX from Migration hardware and powered VMs. Checked all VMs are up and operational, I did the quick migration to actual production storage. Now all my VMs are on Hyper-V. Underneath I have illustrated high-level view of the migration approach

Using Vembu to migration from any Hypervisor to any Hypervisor

Let me share here the actual process with screen captures. Below I’m moving a VMs from VMware to Hyper-V.

Choose VM to restore in Vembu

The second step as I share in the previous blog posts is the restoration type. For the above-discussed use case, I have selected Download.

Choose how to restore using Vembu

In the third step, I chose the version to restore and data to restore (Here it will be full Virtual Machine)

Choose the restore version in Vembu

Choose data to restore in Vembu

In the fourth step, I have selected the format of the disk and where to restore it. The format of disk supports my claims of any to any hypervisor possible. VMDK-Flat is the VMware format and not VMDK. VMDK is for the Oracle Virtual Machine (OVM) platform. RAW is for the KVM, and VHD/VHDX is for the Hyper-V.

Choose the Restore Location and Format for Restore in Vembu

S drive which I have selected in the screen below is the iSCSI disk I presented from the migration hardware. I can select any drive as long as vBDR can see it locally on its machine.

Choose the Restore Location on Backup Server in Vembu

In the review step, I checked all details before clicking Finish.

Review restoration configuration in Vembu

After copying operation is completed successfully; I brought the hardware to destination site. In Hyper-V server, I configured iSCSI initiator and presented the disk from the migration hardware. I create a Virtual Machine in Hyper-V.  I have shown steps which are unique to the process. First, you must select generation-1 hardware; the generation-2 hardware is boot from SCSI which is not recognized by OS when booted from Hyper-v.

Virtual Machine Generations in Hyper-V

Choose Virtual Machine Disk Generations in Hyper-V

Virtual Machine is booted and functioning.

VM successfully Booted using Vembu

Please do not forget to install/upgrade integration services. It is important you update it before handing over VM to operations

Share this:

  1. Facebook

  2. LinkedIn

  3. Twitter

  4. WhatsApp

  5. Reddit

#VHDX #VMDK #vSphere #VirtualDiskFormat #Hypervizor #RAW #HyperV #Vembu #VMDKFLAT #VembuBDRSuitev360 #Hypervisor #VHD #VembuImageBackup #vCenter


©2019 by virtual2Cloud. Proudly created with