Saturday, 19 November 2016

Windows Server 2016 Technical Preview 5 - Cluster OS Rolling (Windows Server 2012 R2 to Windows Server 2016) Upgrade Process - Part 6

Hello Everyone,

In this post, I will help You to understand the migration process of Windows Server 2012 R2 cluster to Windows Server 2016.

Before proceeding to showcase about process, first need to understand different ways to move Your environment infra to 2016.


To see Windows Server 2016 Technical Preview 5 Overview, Click Here!

To see Windows Server 2016 Technical Preview 5 Hyper-V Installation, VM Deployment & What's New in VM Settings, Click Here!

To see Windows Server 2016 Technical Preview 5 Failover Clustering Installation, Configuration & Post Configurations Process, Click Here!

To see Guest Clustering Installation & configuration using Shared VHD (new feature), Click Here!

To see Nested virtualization process (new feature)Click Here!


Let's start understanding different ways below......



DIFFERENT WAYS TO MOVE INFRA TO 2016: 


As per Microsoft, there are multiple ways to move Your environment to 2016... I will explain some of the ways but my explanation way may differ from Microsoft. I will try to explain in very simple language.

Below are some ways to move Your environment to 2016:


CLEAN INSTALLATION:


This process means to install Windows Server 2016 from ISO or EXE file directly. This will install fresh OS on Server and You will loose all Your data or applications which were in older version.

To go for this process, You have to first take backup of all Your data & after clean installation, import the data & re-install all applications.

As per my personal view, this process is not a best practice in Production Environment because this will require long down-time as well.



MIGRATION PROCESS:


Microsoft says that this is the best recommendation process to move Your environment to 2016.

This process helps You to migrate Your roles & features from 1 Server to Another server with same or new features. This is something different process than upgrading Your environment within same server.

Click Here to see Server Role Upgrade & Migration matrix which are supported for Windows Server 2016!


CLUSTER OS ROLLING UPGRADE: 


Another best option to upgrade your complete workload of Hyper-V 2012 R2 to Hyper-V 2016 without down-time which will finish impact on Service Level Agreements. 

This is a new feature of Windows Server 2016 in which You can add Windows Server 2016 node to existing Windows Server 2012 R2 cluster nodes and migrate all roles & clustered disk to Windows Server 2016 Node. 

This process will be complete online process & no down-time is required. Once all work-load is migrated to Windows Server 2016 Node, run a power-shell script to update "clusterfunctionallevel" to 2016 from 2012 R2. (NOTE: Once You update cluster functional level to 2016, You can't roll back to 2012 R2.) 


LICENSE CONVERSION: 



This option is available for upgrading editions of same version. Not applicable for all editions but for some editions. You just need to update License Key using power-shell script to update edition.


UPGRADE:


This option is good for upgrading Your evaluation version to retail version and for virtual environment instead of physical environment. Because many OEM Servers won't support upgrade version to new version. Also, not all older operating system support upgrade options to newer version.


This is all about available options to move Your infra to 2016.


Now, I will show You Cluster OS Rolling upgrade process step by step. This process below shared is based on my personal experience. Microsoft has also shared reference post to upgrade infra using OS Rolling upgrade which You can see by Clicking Here!

May be I missed some steps or may be my process is little different from Microsoft post but concept is similar. That's why for viewers reference, I have shared reference link above for Microsoft Post as well for more clarity.

Let's start with prerequisites....




PREREQUISITES:


As mentioned earlier, this process has very simple process and have minimum prerequisites. Below are the prerequisites:



  • Prepare node(s) with Windows Server 2016 with all configurations similar to Windows Server 2012 R2 clustered nodes like network, firewall etc.
  • Join the Windows Server 2016 node(s) to same domain as of Windows Server 2012 R2 clustered nodes.
  • Share all disks (includes CSV & Quorum Disk which are used in Windows Server 2012 R2 clustered nodes) with Windows Server 2016 node(s).
  • Install Hyper-V Role & Failover Cluster Feature on Windows Server 2016 node(s).

NOTE: Make sure You ready equal number of Windows Server 2016 Nodes based on resources to handle all workloads which is running on Your production Windows Server 2012 R2 Clustered nodes to maintain availability & SLA service.

CHECKLIST:


  • Make sure Your hyper-v 2016 node CPU support Second Level Address Table (SLAT). You can download Coreinfo Tool from this link to check if node CPU support SLAT!
  • All Clustered nodes must be up & running.
  • All Disks (CSV & Quorum) must be shared with Windows Server 2016 node as well.
  • If you are running CAU then make sure it is running. Use power-shell script to check: Get-CauRun.

CLUSTER OS ROLLING UPGRADE PROCESS:


After completing all pre-requisites shared above, check if all nodes are running in Window Server 2012 R2 cluster:





Add Windows server 2016 node to existing Windows Server 2012 R2 cluster nodes by clicking on Add Node:





Give Windows Server 2016 Node name:




Next step is validation warning. Don't validate this node. Just make sure You have all prerequisites ready like network configuration similar, all disks shared & firewall setting off. Why I am saying not to validate this step is because this will fail with message that OS version is different as shown in below report status:





Select No for validation warning step:





Click Next:





Click Finish:





Windows Server 2016 Node is successfully added in Windows Server 2012 R2 cluster:





This is all about the best feature. Now You can live migrate Your resources to the Windows Server 2016 Nodes (Disks & VM Roles) by selecting them, click on Move/Live Migrate & Clicking on Select node option:





Select Window Server 2016 Node:




Disk will be moved to Win 2016 node with no down-time:




Similarly, Live migrate all VMs to Windows Server 2016 node:





Once all VM Roles & Disks are migrated to Windows Server 2016 node, You can evict Windows Server 2012 R2 nodes from cluster one by one:





Click Yes:






After removing all Windows Server 2012 R2 nodes from cluster, You have only windows server 2016 node(s) in cluster with all Roles up & running with no time.


Now, You have to update "clusterfunctionallevel" to Win 2016 by running below power-shell script from any win 2016 node:

Update-ClusterFunctionalLevel -Cluster <"Cluster_Name"> as shown below:




Type "Y" & then click enter. Your cluster functional level will be upgraded to 2016. Now, You can format old windows 2012 R2 server & install windows 2016. Later add them to Windows Server 2016 cluster after completing all prerequisites.




This is the easiest way to upgrade Your infra to 2016 with zero down-time. :)


Share Your feedback or any query!!!


Happy Reading!!!

If You like my post then follow my updates:


Join my Facebook group for updates on trending technologies/technical references/issues etc:


No comments:

Post a comment