Virtual Machine Migration Toolkit

Microsoft at MMS 2012 announced a new toolkit for mass conversion of VMware VM’s to Hyper-V. VMMT is wizard based conversion tool aimed at conversion from VMware to the current version of Hyper-V. Windows Server 2012 support is still under development.

Please note that this is a different tool from the Microsoft Solution Accelerator called Microsoft Virtual Machine Converter.

If you are only converting a dozen or so VM’s it is not worth your while. However if you have 100+ Windows and Linux VM’s in your environment this tool is for you. The target customer has multiple hypervisors, wants to move to Hyper-V and has primarily a Windows workload.

VMMT as it is called uses a combination of existing products and custom scripts:

  • vCenter & vSphere
  • Veeam Backup and Reporter
  • Orchestrator 2012
  • PowerShell
  • Virtual Machine Manager 2012

image

Microsoft and Veeam worked closely together on this project. Veeam have been a VMware Platinum partner for years but when they saw that adoption of Hyper-V was beginning to pick up, they now broadly support Hyper-V.

The contribution of Microsoft consists of:

  • Virtual Machine Manager
  • Orchestrator
  • Web UI
  • Runbooks

Veeam contributed:

  • 6 months Reporter license
  • 6 months Backup license
  • 90 day eval of nWorks
  • Script used by Runbooks

Currently the following operating systems are supported:

  • Windows 2008
  • Windows Server 2008 R2
  • Windows 2003 SP1+
  • SUSE
  • CentOS
  • RedHat

Sources:

  • vSphere 4.1
  • vSphere 5.0

Other operating systems may work but were not in scope at the start of this project.

There are also a number of limitations:

  • VMs in VMware with IDE Virtual Hard Disks
  • VMs in VMware using RDMs
  • Static IP is not automatically configured in target
  • Limited to four virtual disks on IDE bus (V2V limitation)

There are both online and offline conversion options.

The VMM Migration Toolkit starts with a running machine and uses Veeam to create a copy of the VM without interrupting the production VM. VMMT then does a number of preparations, performs the conversion, creates a copy of the VM to the VMM Library (using NFS to mount the copy), deletes the conversion files, detects the operating system, run the V2V, remove the VMware tools from the VM and finally collects networking info.

The virtual machine that is being converted has to stay offline until the process is completed. A very interesting aspect of this toolkit is that it extensively uses Orchestrator runbooks.

image

image

It is important to note that currently support is limited to USA & Canada, Germany, UK and Australia and you need to contact your Microsoft Sales Rep. Involvement of a partner or MCS is required.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">