{"id":531,"date":"2017-05-12T04:46:36","date_gmt":"2017-05-12T02:46:36","guid":{"rendered":"http:\/\/itsimple.info\/?p=531"},"modified":"2017-05-12T04:47:57","modified_gmt":"2017-05-12T02:47:57","slug":"upgrade-2012-r2-cluster-to-2016-using-cluster-os-rolling-upgrade","status":"publish","type":"post","link":"https:\/\/itsimple.info\/?p=531","title":{"rendered":"Upgrade 2012 R2 Cluster to 2016 using Cluster OS Rolling Upgrade"},"content":{"rendered":"

Upgrade 2012 R2 Cluster to 2016 using Cluster OS Rolling Upgrade<\/h1>\n

mirrored from : http:\/\/www.altaro.com\/hyper-v\/upgrade-2012-r2-cluster-2016-using-cluster-os-rolling-upgrade\/<\/h6>\n

Starting with Windows Server 2016 we get a new, nice feature which makes the cluster upgrade job a lot easier and cheap. And to be honest, it was about time. In previous server versions if we wanted to upgrade a Windows cluster we had to build a new one with at least one host in it, then migrate the virtual machines, reinstall the old hosts with the new OS then attach the hosts to the new cluster. With server 2016 it\u2019s a little bit easier but we still have some work to do, like re-configuring networks, Hyper-V settings, storage, etc. At least we don\u2019t need to get downtime for our virtual machines and don\u2019t need extra hardware.<\/p>\n

Now that I\u2019ve mentioned all the goods, it\u2019s time for the bad ones also, which are actually just one: we need to have at least Windows server 2012 R2 running in the current cluster. This means that if our Hyper-V cluster is running 2008R2 or 2012 for that matter, we will need to use the old method to upgrade the cluster<\/a>. To make it even easier, I have copied a nice upgrade process workflow from Technet<\/a> which shows the steps that need to be followed in order for the upgrade to be successful. Before we move forward make sure you have sufficient capacity on the cluster to maintain the workload since the upgrade requires removing one node at a time from the cluster. Also, make sure that the running Hyper-V nodes are compatible with server 2016, or Microsoft support will hung up on you.<\/p>\n

\"upgrading-server-2012r2-cluster-to-server-2016_01\"<\/p>\n

Stopping Cluster Aware Updating and backing up data<\/h2>\n

The first task is to backup the cluster database and the workload data. Now I\u2019m not going to show this here since it\u2019s out of the scope of the article, but all you have to do is backup the system state of your Hyper-V servers, then the virtual machines that are running on them using your favorite backup software<\/a>. The next step will be to check if Cluster Aware Updating (CAU) is running or not. If it\u2019s running, it needs to be stopped, so the cluster nodes are not paused, drain, or rebooted by this service. From the Administrative Tools<\/strong> menu click the Cluster-Aware Updating<\/strong> icon and take a look if there are servers in pending or updating state. If they are click the Cancel Updating Run<\/strong> option to stop the process.<\/p>\n

\"upgrading-server-2012r2-cluster-to-server-2016_02\"<\/p>\n

PowerShell can also be used to check this, if you are a PowerShell savvy. The command needs to be executed from one of the cluster nodes, else the -ClusterName<\/strong> parameter needs to be specified followed by the cluster name.<\/p>\n

\n