3 Easy steps to migrate to Hyper-V 2012 R2

Hyper-V is cool! Its technically sound and for all practical purposes has become an excellent choice for running infrastructure workloads in a virtual environment. Hyper-V is not just for test and development environments anymore. More and more businesses are relying on Hyper-V to run their production workloads like Exchange, SQL, SharePoint, and Active Directory. Production environments have strict operating requirements! Business relies on uptime and access!

So what if you were using Hyper-V in Windows Server 2008 R2 to run your Virtual Machines (VMs) and you have decided to make the move to Windows Server 2012 R2? How will you migrate those VMs? I get this question at least once a week so I decided to write the detailed answer.

For those of you who are thinking “Oh, that’s easy I would simply upgrade the Hyper-V host from Windows Server 2008 R2 to Windows Server 2012 R2, while preserving the original file system, and then import the virtual machines to Hyper-V on Windows Server 2012 R2.” That’s an excellent answer if you can accept the potential data loss and certain VM downtime associated with it. I am going to operate under the assumption that this is a production environment and the in-place OS upgrade and VM import migration is not really an option. In the world of data protection we are always looking to improve our Recovery Time Objectives (RTO), and Recovery Point Objectives (RPO). In short, we cannot risk downtime or data loss.

Enter Veeam Backup & Replication! This tool lets you manage the 3 challenges of migration, downtime, and data loss, and do it in a way that is Powerful, easy-to-use and affordable.

Veeam Backup & Replication is built to be used ONLY in virtual environments. Specifically Veeam Backup & Replication supports both Hyper-V (in all its editions and versions) and VMware in the same interface. As the name suggests there are 2 key functions that each of you will want to perform as part of your migration from Windows Server 2008 R2 to Windows Server 2012 R2.

#1 Backup your existing VMs – Veeam has built the best backup solution for virtual machines running on Hyper-V. Everything associated with the VM including the .vhd or .vhdx, binaries, settings (such as the registry entries and XML data), snapshots etc. is backed up into a single compressed and deduplicated .vbk backup file. The backups complete quickly and without the need for pausing, stopping or otherwise interrupting the operation of the VM. These backup files are completely portable and easy to recover very quickly if the need should arise. I have seen several customers accomplish migration using only Veeam Backup.

#2 Install Windows Server 2012 R2 with Hyper-V – Complete the install of the new Windows Server 2012 R2 Hyper-V host in your environment and then add the host to your Veeam console.

#3 Build a replica of the VMs on Windows Server 2008 R2 on the new Windows Server 2012 R2 Hyper-V host. – Replicas are exact copies of virtual machines that are updated or synchronized with the original VM on a regular schedule. These replicas act as a point of failover and provide significant RPO benefits that do not come from backup alone. There is a great Blog post here on the process of building the replicas.

With replica VMs in place and completed backups on production storage, you are now ready to complete the migration process with acceptable RPO and RTO risks. In short, you have eliminated most of the downtime and data loss risk from the process of migration.

At this point the migration is easy. You can simply run a permanent failover from the source VM to the target VM and the migration will be complete without interruption to the production workload running on the VM. The best part is, it’s all wizard driven. Take the figure below, if you can find your VM and click next you can leverage the replication engine to migrate to the newer Hyper-V host:

When it comes to migrating VMs from Windows Server 2008 R2 to Windows Server 2012 R2 you really want the ease and power that come from using Veeam Backup & Replication.

An additional yet very important benefit of using Veeam Backup & Replication to migrate VMs from Windows Server 2008 R2 to Windows Server 2012 R2 is that you can fail back to the 2008 R2 environment. This option goes away when you do an in-place upgrade of your hosts.

It’s important to have options, and if you are like me you’ve made changes to your Hyper-V hosts and storage along the way. This may be a good opportunity to start clean with a new configuration for your VMs. Maybe you want to run VMs on SMB 3.0 shares, maybe it’s time for a CSV cluster or maybe you want to put your local storage to work for some VMs. Either way, migrating the VMs with Veeam Backup & replication makes this an easy task.

**Veeam Backup & Replication has built-in support for PowerShell Scripting complete with a set of cmdlets that you can use to help you automate this process.

See also:

Get weekly blog updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam’s Privacy Policy
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our blog with this weekly digest.

Eliminate Data Loss
Eliminate Ransomware

#1 Backup and Recovery

Start free trial


  • WRAR says:

    How about single node hyper-v 2012 vm’s in place to 2012r2, where the host server is already on 2012 R2… Is that now possible unlike 08r2?

  • mlevkina says:

    I would say that if you have only one Hyper-V host, you will expirience VM downtime in any case. The classical approach is the following: VeeamZIP VMs on an external storage, upgrade the host and restore VMs.

  • aurang zaib says:

    on vaeem site should be a live chat messenger for help and support to public for genral queries

  • JS says:

    Does this guidance change coming from 2008?

  • JS says:

    What about VMs on a hyperv 2008 R2 host/cluster to hyperv 2016 host/cluster? Will VEEAM backup and replication support Windows Server 2016 at RTM?

  • JS,
    We will support ws 2016 as soon as possible (our track record is always 90 days or less after RTM, after final testing with the GA code of windows server). But migrating from 2008 R2 to 2016 won’t be that easy I’m afraid as a lot is changed in 2016 where the VMs have a different hardware level, different config file format and so on…

  • JS says:

    Thanks for the quick response Mike. I was hoping VEEAM backup/rep. could be used as not only a b&r tool but a migration tool as well. However other potential migration tools seem to be affected by the changes coming in 2016 as well.

  • Hi JS,
    At this point in time we don’t know it for sure. As said, the VM level between 2016 and 2008 R2 is very different and since 2016 is still in technical preview things can change. Logically speaking you should be able to restore a 2008 R2 VM to a 2016 host, but after that, it will require some downtime of the VM to upgrade the VM to the latest hardware level. And this is something we can’t do online because of the way Microsoft has made changes. To be continued, and we will see more later on when we reach GA

  • Brian says:

    How about migrating from vmware to hyper-v? I don’t suppose we have backup and restore capabilities from one hypervisor to the other. Dreaming I know but that would be awesome.

  • Andrew Zhelezko says:

    No, we don’t. For this, you should use V2V converter (VMM, 5nine, StarWind to name a few) and schedule some outage time for the VMs in question.

Leave a Reply

Your email address will not be published.