Cluster OS Rolling Upgrades in Windows Server 2016
Cluster OS Rolling upgrade is a new feature in Windows Server 2016 failover clustering. If a Windows server 2012 failover clusters running the Hyper-V or Scale-Out File Server roles, you can add Windows Server 2016 nodes without taking the failover cluster offline. In earlier Windows Server versions, you had to create a new cluster with the new operating system on all nodes, and then you had to move the clustered services over to the new cluster. This created downtime and made it difficult to quickly complete upgrades. With Windows Server 2016, cluster nodes do not require additional hardware to upgrade, you can take one node at a time offline, upgrade the operating system, and bring the node back into the existing cluster. This changes the cluster to a mixed operating system mode. The process is fully reversible- Windows Server 2016 nodes can be removed from the cluster and Windows Server 2012 R2 nodes can be added to the cluster in this mixed mode. After you upgrade all nodes, you can change the functional level of the entire cluster from the Windows Server 2012 R2 version to Windows Server 2016 version. Cluster OS Rolling Upgrade Process This section describes the workflow for performing Cluster OS Rolling Upgrade. Image copy from TechNet. Before you start Cluster OS Rolling Upgrades, first we should backup cluster database and workload data. Then, verify that Cluster Aware Updates (CAU) is currently running by using Get-CauRun cmdlet. If CAU is currently running, use CAUStop-CauRun cmdlet to stop Cluster Aware Update (CAU). Stopping Cluster Aware Update (CAU): If you are running Cluster Aware Update (CAU), verify use the PowerShell, Get-CauRun cmdlet. To stop CAU use the PowerShell, Stop-CauRun cmdlet. But in this demo, you have not installed Cluster Aware Updates (CAU). So it’s WARNING: No Updating Run is currently in progress on cluster. Verify that all cluster nodes state are Up before remove Node from the Cluster: Using the cmdlet, Get-ClusterNode to verify the cluster nodes State.
Updating the Cluster Functional Level:
Until the Update-ClusterFunctionalLeve cmdlet to run, cluster runs in mixed mode, this process is fully reversible and Windows Server 2012 R2 nodes can be added to this cluster and Windows Server 2016 nodes can be removed.
8= Windows Server 2012 R2 Functional Level (compatibility or mixed-OS mode)
9= Windows Server 2016 Functional Level
Use Get-Cluster | Select ClusterFunctionalLevel to display state
Windows Server 2016 makes upgrading clusters easy with rolling upgrades. I hope this article help you Windows Server 2016 Cluster OS Rolling Upgrade configuration.
If the ClusterFunctionalLevel value set to 8, then the cluster at Windows Server 2012 R2. Now Remove NODE 2, Windows Server 2012 R2 from the cluster: Ensure that the VMs are migrated from NODE2 to NODE1 in the failover cluster before you can evict NODE 2 from the failover cluster. Verify all the VMs are in NODE1, KTM-HOST1. Suspend the node from the cluster using PowerShell: Remove the node from the cluster using PowerShell: In the Cluster Events Details, make sure that “Cluster node KTM-HOST2 has been evicted from the failover cluster”. Remove the Server from the Domain, Clean Installation of Windows Server 2016, and Configure Server Name and Add the Server to the Domain, msservepro.com. Add the Node to the original Cluster (node rejoins the cluster) using PowerShell We can also add the node to the cluster by using the PowerShell cmdlet Add-ClusterNode. After the Windows Server 2016 node is successfully added to the cluster, you can (optionally) move some of the cluster VMs to the newly added node in order to rebalance the workload across the cluster using Move-ClusterVirtualMachineRole cmdlet given below:
Related Post Remove a Node from a Windows Server 2016 Hyper-V Cluster and Destroy a Cluster Procedure
|Move-ClusterVirtualMachineRole -Name KTM-DB1 -Node KTM-HOST2|