VMware to Hyper-V Migration
There probably hasn’t been a larger impact on IT efficiency in the last decade than virtualisation. With more and more solutions coming onto the market; it’s not uncommon to be running different versions in your environment. However; while it’s common to want to move guests from VMware to Hyper-V – it doesn’t mean it’s not a challenge.
We’ll be covering the main steps to consider if you’re looking at migrating from VMware to Hyper-V in your environment.
There are a few things to take into consideration before migrating your virtual machines. The first major question is exactly how many VM’s are to be migrated?
There are many great tools available for performing bulk migration of VM’s which may assist with the completion of the task.
The second important area to be wary of is downtime. Regardless of how efficient you’re migration is; there will be some downtime occur. As we all know; downtime does have costs involved to the company.
It’s also a good idea to document the VM configuration before starting any migration process. This just makes it easier to refer back to at a later stage if required.
Initial Tasks – Prepare your VM’s for migration
This is essentially stripping the VM down to basic requirements and reduce the potential impact on the actual migration process. This is considered best practice when performing a VMware to Hyper-V migration. Part of this process should be to:
Remove all CD’s that are connected to the VM: Having such media attached to a VM when it’s being migrated has been known to cause problems (and add additional time to completing the overall process).
Check for and remove any unnecessary virtual hardware: Depending on how long the VM has been in use; it’s not uncommon for it to have additional virtual hardware attached for whatever reason. Additional serial ports, SCSI ports and multimedia hardware (such as sound cards) can bloat a VM.
Clean up disks of any unwanted data: This is a pretty basic task. If you’re anything like us; you’ve never cleared the recycle bin within the OS; or uninstalled older applications that may no longer be in use.
Some will also suggest that performing a defrag on all the volumes is a good practice to get into the habit of as well.
Commit all snapshots (if you’re using them): While we don’t necessarily recommend using snapshots in a production environment; sometimes they are required depending on the purpose of the VM. The reason why these should be committed (or reverted if you wish); is that such snapshots aren’t able to be migrated from VMware to Hyper-V easily.
Let the VMware to Hyper-V Migration Begin!
We’re going to assume you’ve already installed your favorite Windows OS; and installed the Hyper-V role so that it’s ready for running VM’s.
You’ll need to select a migration tool that will convert the VMDK (VMware) files into VHD or VHDX (Hyper-V compatible file format). Two that we’ve been quite impressed with in the past is the Microsoft VM Converter tool and also StarWinds V2V converter.
Once you’ve converted the necessary VMDK files to VHDX; you should be able to attach these two a VM within Hyper-V and boot successfully.
About Test My Backups
Test My Backups is an IT service provider that is solely focused on data protection for businesses. Our staff have worked with businesses of all sizes over a number of years; helping them untangle and streamline their backup and data protection strategies.
If you found our VMware to Hyper-V Migration article helpful; give us a share on your different social platforms below. Have a suggestion for another article you’d like to see? Drop us a line and we’ll get to work on it straight away!