Many organizations are starting to realize the value and benefits of Microsoft’s Hyper-V platform. Once you have made the decision you might be wondering how to plan your migration. The first step in any migration effort is identifying what is in your environment. For a migration to Hyper-V, this means that you need a solid inventory of your existing VMware environment. When we perform migration planning for organizations there are two primary tools that we use to identify what is currently running. The first is Xtreme VM Migrator. Xtreme VM Migrator provides a quick inventory of the VMware environment and pulls detailed information from all of your running virtual machines. Xtreme VM Migrator can be run as a standalone or be integrated into System Center Orchestrator with pre-built Actions and Orchestrator Runbooks. Below is an example of the runbook that gathers all virtual machines:
Runbooks are simple to use. To use the referenced runbook, you first go to Properties of each of the Actions, then provide the details of your VMware environment including the name of VMWare vCenter Server and the usernames/passwords needed to connect. When the runbook starts, Xtreme VM Migrator will connect to your VMware environment, storing all of the virtual machine details in a database that is able to be reported on or modified as needed. After the information is gathered, we’ve created two reports that are extremely helpful in planning your migration:
- VM Inventory: Full details for every running virtual machine in the VMware environment
- Unsupported: A list of the machines that will not be supported for migration due to BIOS levels, OS Levels, etc.
The report generates both a CSV file and an HTML file that will show you the details of the virtual machines. Here is a sample listing of a VM inventory:
This report shows items like the hard drive size, memory, processor, NIC Information, etc. One of the most important pieces of information to notice is the Provisioned Hard Drive size. The full provisioned sized disk is initially created in Hyper-V during the migration; however, there is also a backup performed on the VMDK file(s) so it’s necessary to plan for double the storage of a given virtual machine’s Provisioned Hard Drive size during the migration process.
Now that you have a basic inventory, you may be interested in getting more detailed information on how to potentially consolidate resources and reduce the memory and processor footprints for your virtual machines. More detailed information is generally gathered using the Microsoft Assessment and Planning (MAP) Toolkit. MAP pulls detailed usage information from virtual machines including the current software running. MAP will also provide recommendations on reducing the number of virtual processors or memory based on your usage load and the hardware that is hosting your new Hyper-V environment. Obtaining an actual workload inventory is important because some machines may not be a good fit for migration. Examples include:
- Older systems that are running Windows Server 2003
- Domain Controllers – These can be rebuilt and its information can be easily replicated
If MAP suggests reducing the virtual machine memory or processor, you’re able to modify the Xtreme VM Migrator database and change values for a virtual machine. When the migration occurs, the values from the database will be used to create the new virtual machines in Hyper-V – we’ll cover more on this topic in later posts.
As you’re able to see, getting detailed information about your environment is not complex but it is crucial in planning your migrations from VMware to Hyper-V.