VMware to Hyper-V > Mass migration and Live VM Migration

[vince154]

Hello,

I'm planning to replace my old VMware Cluster by a brand new Cluster on Hyper-V with VMM
The cluster runs around 450 VMs.

As I'm looking for tools to convert VMs, I found pros and cons to each tools (based on information found on the Web)

• VMM
  • Advantage : Integrated Management of VMware during the migration and optimized conversion time
  • Disadvantages :
    • One VM at a time
    • VM needs to be switched off (and Vmware tools uninstall) so long time of service breakdown

• Veeam Backup
  • Advantage : Mass conversion with Instant Recovery feature
  • Disadvantages :
    • VM needs to be switched off (and Vmware tools uninstall) so long time of service breakdown

• Starwind
  • Advantage :
    • Performing live VM Migration
    • Windows Repair mode allowing to remove VMware Tools after migration
  • Disadvantages :
    • One VM at a time (in GUI mode)

I'm very (very) interested in Starwind tool. I just looking for more accurate information about

• Live VM Migration : How it works ? what are the prerequisites ? etc.

• Command-line : is it possible to schedule a multiple-VM migration through a script ? If so, do you have any script example ?

Can you help me with the questions above and confirm the pros of the starwind solution ?

[yaroslav (staff)]

Thanks for your post!

Live VM Migration : How it works ? what are the prerequisites ? etc.

The VM should have no snapshots.
V2V converter creates a checkpoint before creation, converts the disk and merges the snapshot at the end.

Command-line : is it possible to schedule a multiple-VM migration through a script ? If so, do you have any script example ?

Mass conversion in GUI is to be introduced later. Now it is only one VM at a time.
Sadly, there is no ready-to-go script for conversion, yet, theoretically, you can use multiple CMD sessions to run several conversions at a time.

[vince154]

Hello,

Thanks for the reply. It helps a lot ! I think I would try the automatisation using the CLI.

V2V converter creates a checkpoint before creation, converts the disk and merges the snapshot at the end.

After reading your comment, I guess that the source VM is automatically shutdown after the "first "conversion in order to merge the snapshot. Is that correct ?

I also read about the Windows Repair Mode after conversion for Windows VMs. What about Linux VMs ?

[yaroslav (staff)]

Hi,

You are always welcome!
No, the VM can continue running (I V2Ved a running VM last weekend).

[Nerund86]

How does this V2V thing work?

[yaroslav (staff)]

It converts the VMs and their disks between the hypervisors.