This is a followup to: Migrating From Physical to Virtual Servers. As we mentioned earlier, there are other migrations supported by Vembu BDR other than P2V and V2P.
There are two major players in the virtualization environment:
- VMware
- Hyper-V
Vembu introduced support for virtual migration as a feature in Vembu BDR. This allows Vembu users who have backed up their VMs from the VMware environment to migrate easily as Hyper-V VMs. There are two major options available for this migration to occur, they are:
- Instant Boot: This option lets users receive their VMWare backups instantly booted on a Hyper-V machine as VMs. This only takes minutes to complete the migration and will be more helpful at times of business continuity when a VM is down.
- Download as a VHD: This is an option that lets users have their VMWare backup downloaded as a VHD file, which can be installed on a Hyper-V machine as a VM. The major difference between instant boot and download as the VHD option is that in the instant boot option, the mounted backup data is virtually mounted. So the changes made in VMs on the Hyper-V environment will be stored separately leaving the original data unaltered. But in download as VHD option, the changes made in the VM on Hyper-V environment will be stored on the VHD file itself which lets the user resume work where it was left off when the VM restarted.
We have also introduced a feature to resume jobs in instant booting, however it needs virtually mounted backup data to get the VM created. Whereas in the case of the download option, you can get the VHD file to an offline server and there you can get your Hyper-V VMs working.
If you have questions on VMWare migration to Hyper-V environment, please drop us an email at vembu-support@vembu.com. We also have a final migration process left to explain so stay tuned.
