Ok, it´s a bit late for such a post since Windows Server 2012 R2 is out for over six month now, but still here are some rough steps from the upgrade of my demo 2012 Hyper-V cluster to Windows Server 2012 R2.
High Level Steps
To do this, I need to remove a existing node from the current 2012 cluster, install 2012 R2 on it and build a new single node cluster. Then move the VMs from the old cluster to the new cluster. Once finished, destroy the old cluster, install 2012 R2 on the free node and join it to the R2 cluster. Since I use VMM, I will try to leverage VMM as much as possible to make the transition easy. These steps are done in VMM:
- Add the R2 server as a host to VMM, which also installs the Hyper-V role
- Setup the virtual switch using a logical switch in VMM, which configures all the converged network settings for me
- Setup the new R2 cluster using the VMM cluster wizard
It´s important to notice that you need additional shared storage for the new cluster. At least one drive for Quorum and one for a CSV disk.
The cluster notes use a converged network of three NICs for Live Migration, Cluster CSV, Management and VM traffic. iSCSI is connected via separate physical NICs.
In this environment I am also using System Center Virtual Machine Manager 2012 SP1. So this needs to be upgraded as well. This post captures the high level steps I performed:
Upgrade of System Center Virtual Machine Manager 2012 SP1 to 2012 R2
- Uninstalled VMM 2012 SP1 using Retain Database from the VMM server
- Uninstalled the ADK 8 from the VMM server
- Upgraded the VMM server to Windows Server 2012 R2
- Installed ADK 8.1 on the VMM server (Deployment Tools and Windows Preinstallation Environment features)
- Install VMM 2012 R2 using the retained VMM database
- Follow the post-upgrade tasks found here: http://technet.microsoft.com/en-us/library/dn469629.aspx
Fresh install of Windows Server 2012 R2 on the first cluster node (HV01)
- Evicted cluster node1 from the cluster (in my case the rest of the cluster run on just one node)
- Remote the cluster node1 from VMM
- (Remove the virtual switch and the virtual management OS network adapter from the host)
- Started Windows Setup from the DVD
- Renamed the network adapter to make sense and set up TCPIP correctly on one of the NICs
- Renamed the server and joined the server to the domain.
- Run Windows update
- Configured iSCSI NIC adapter (for the new cluster
Bring first cluster node (HV01) under control of VMM
- Configured the networking on the host. Since I used logical switch configuration I could apply the already created logical switch to the new Hyper-V host quite easily. First I configure the NICs in the team, then I configured the virtual network adapters:
In the Logical Network view I can now see that the HV01 host has been configured with the Logical Network configuration and that the host is compliant.
On the host itself, there is now a NIC team and the virtual network adapters as specified in the Logical Switch.
- Note, that although I name the host management adapter in the logical switch configuration “HostManagement”, in the Network Connection panel it´s named vEthernet (Converged Switch), which is the name of the switch not the adapter. The other adapters like ClusterCSV or LiveMigration are named according to the name that I specified in VMM. This is by design, I guess.
Also, it´s interesting how VMM 2012 and VMM 2012 R2 name the team adapter in Windows. In VMM 2012 the team adapter is named “ConvergedSwitch6b858dbe-fefc-4ecc-994e-e1587551422b” in VMM 2012 R2 the adapter is simply named “ConvergedSwitch”. I always thought that the VMM 2012 naming was a bit strange.
Create a New Hyper-V Cluster from VMM
- I created two new LUNs on the storage for the new cluster (called R2Cluster) that I am going to create using HV01.
- Connected the HV01 host to the iSCSI target and set up a LUN for the Quorum and a LUN for VM storage (I called it CSV3)
Copy the VM Role from the current Cluster to the new Cluster
- I went to the cluster node of the new cluster and started the cluster manager. I used the Copy Cluster Role link to start copying the VM roles.
The copying of the roles is very quick. At this point the roles are still running on the current Cluster.
- Now I stopped the VMs on the current cluster. I put the CSV where the VMs are located in Offline mode. Next I had to connect the new cluster node to the iSCSI Target where the CSV was located. Once that was connected, I brought the CSV online on the new cluster node.
Once all the rules have been moved to the new cluster, I started removing the cluster service from the old cluster and clean up all the relevant VMM and Hyper-V components. Then the old cluster node was reinstalled with Windows Server 2012 R2 and joint the new R2 Cluster.