Migrating VM
To be agile and competitive a contemporary IT environment needs a clear migration path across different
hypervisors. There are two major virtualization software vendors on the market right now, i.e. VMware and
Microsoft. Compared to hypervisors from VMware, Microsoft Hyper-V has the great advantage of being included
with Windows Server at no extra cost and providing tight integration with Microsoft Azure, which really makes
sense for a switch.
With Hard Disk Manager you can easily migrate your virtual machines from VMware vCenter, ESX or ESXi servers
directly to Microsoft Hyper-V environment.
This is an offline migration scenario, so your VMs won’t be available until it is over. The total
amount of downtime depends on the size of VMDKs to be processed.Recommended actions before you start the migration:
- Remove ISO-images, attached to the target virtual machines to avoid any disruptions.
- Check for the presence and remove unnecessary hardware inside the target virtual machines.
- Clean up the target virtual disks (empty the trash, delete unused apps, defrag the source volumes).
- Delete snapshots for the target virtual machines to convert "proper" VMDKs only, but not all differencing disks
created by snapshots.- Click VM Migrate on the sidebar, then click the plus icon.
- The Task steps list will appear to the right of the bar. First, you need to set up general migration options.
- Continue the migration when unable to copy any of the source VMs. Unmark this option, if you’d
like our program to stop after failing to transfer any of the target virtual machines, otherwise the
migration task will continue processing all specified VMs. - Shut down the specified source VMs before the migration. Our program can only transfer powered
off virtual machines. Use this option to let our program automatically power off a running VM(s)
involved in the migration process. - Target VMs power status after the migration. By default, the target virtual machines will be powered
on automatically on the destination host after the migration is over. Change this behavior if necessary
by selecting the corresponding option from the drop-down menu.
- Continue the migration when unable to copy any of the source VMs. Unmark this option, if you’d