Migrate Hyper-V to Windows Server 2012 R2 from Windows Server 2012
Updated: August 25, 2014
Applies To: Windows Server 2012 R2
With Hyper-V, you can create a virtualized server computing environment by using a technology that is part of Windows. This guide provides information and instructions about migrating the Hyper-V role that include virtual machines, data, and operating system settings from the source server running Hyper-V in Windows Server 2012 to the destination server that is running the Windows Server 2012 R2 operating system.
Did you know that Microsoft Azure provides similar functionality in the cloud? Learn more about Microsoft Azure virtualization solutions.
Create a hybrid virtualization solution in Microsoft Azure:
This guide describes how to migrate the Hyper-V role by providing preparation, migration, and verification steps.
Migration documentation and tools facilitate the migration of server role settings and data from an existing source server to a destination server that is running Windows Server 2012 R2. By using the tools that are described in this guide, you can simplify the migration process, reduce migration time, increase the accuracy of the migration process, and help eliminate possible conflicts that might otherwise occur during the migration process.
In addition to the migration options that are described in this topic, Virtual Machine Manager in Microsoft System Center 2012 R2 can facilitate and automate a considerable part of the migration process. For more information about Virtual Machine Manager, see Virtual Machine Manager.
This document is intended for information technology (IT) professionals who are responsible for operating and deploying Hyper-V in a managed environment.
Migration of Hyper-V from one server that runs Windows Server 2008 R2 to another server that runs Windows Server 2012 R2.
Instructions for migrating more than one server role at one time.
Migration of Hyper-V from one server that runs Windows Server 2012 R2 to another server that runs Windows Server 2012 R2. Instead, this process is supported by Hyper-V management tools and features. The general process is as follows:
Determine whether to use export and import or live migration to move the virtual machines:
Export and import can be used in either a workgroup or a domain environment. In Hyper-V running on Windows Server 2012 R2, you can now export a running virtual machine.
Live migration requires a domain environment and some additional configuration, but the virtual machine is running throughout the move process.
Add the Hyper-V role to the destination server. You can configure the default storage locations and live migration when you add the role.
Configure virtual switches, and optionally, other networking features on the destination server. Management tools include the Windows PowerShell cmdlets New-VMSwitch and Set-VMSwitch, and the Hyper-V Virtual Switch Manager in the Hyper-V Manager console.
Move the virtual machines by using export and import or live migration. Management tools include the Windows PowerShell cmdlets Export-VM, Import-VM, and Move-VM and the Export, Import, and Move menu commands in the Hyper-V Manager console.
This guide provides you with instructions to migrate a server that is running Hyper-V in Windows Server 2012 to a server that is running Windows Server 2012 R2. This guide does not contain instructions for migration when the source server is running multiple roles. If your server is running multiple roles, we recommend that you design a custom migration procedure that is specific to your server environment and is based on the information in other role migration guides. Migration guides for additional roles are available on the Windows Server Migration Portal.
The Hyper-V role does not depend on any other roles. As a best practice, we recommend that no other roles are installed on a server running Hyper-V.
The following migration scenarios are not supported:
Virtual machine configuration under one of the following conditions:
When the number of virtual processors that are configured for the virtual machine is greater than the number of logical processors on the destination server.
When the memory that is configured for a virtual machine is greater than the available memory on the destination server.
Hyper-V role migration involves moving the virtual machines, virtual networks, and all the associated settings from one physical computer to another physical computer in the enterprise. The process supports moving from a server running Hyper-V in Windows Server 2012 to a server running Hyper-V in Windows Server 2012 R2. The Hyper-V role does not depend on any other roles.
The migration tools include Windows PowerShell cmdlets that you can use to perform some of the tasks that are required to migrate the Hyper-V role and script or to automate the migration process.
In previous versions of Hyper-V, you were required to shut down a virtual machine before you moved it to a new server. If the move was performed correctly, downtime was limited, but still, there was downtime. A new feature in Windows Server 2012 R2, cross-version live migration, supports moving a running virtual machine from Windows Server 2012 to Windows Server 2012 R2. The Windows PowerShell Export-VM cmdlet captures the majority of the Hyper-V settings that are required to perform a successful migration, which includes the virtual machine configurations, virtual networks, and virtual hard disks. Now you can decide how to move virtual machines to Windows Server 2012 R2, where in the past, your options where limited.
The following options are available to move a virtual machine:
Cross-version live migration
Export and Import
Copy Cluster Role Wizard
For additional information about each option, see Hyper-V: Migration Options.
This guide explains the migration process for the following three main scenarios:
The length of time it takes to migrate the Hyper-V role depends on the size of the data to be transferred and on the tools that are used. Of the various types of files to be transferred, the virtual hard disk (VHD), .vhd and .vhdx files, have the largest file sizes from a few gigabytes to many gigabytes in size. The length of time that is required for migration is largely affected by the size of the VHD files and by the network bandwidth.