Summary: This article has been contributed by Ryan Doon, a PFE working with Microsoft Canada. In this post (the first of a two part series), he talks about the new Cluster Aware Updating feature of Windows Server 2012, and how it can be used to easily update clustered servers while maintaining availability of service to clients.
Windows Server 2012 is yet another great addition to the Microsoft product family. I always get asked the question “What are the differences between server 2008 and 2012?” For that reason I will be making various posts either comparing features in 2008 to how it has been improved in 2012, or an overview of new features in 2012.
In a previous post I discussed the best practices for patching Windows Server 2003 & 2008 clusters. Previous to Server 2012, the best method for patching clusters was the manual method. Relying on scripts or third party tools would not always ensure that patching proceeded as expected. The purpose of this post is to give you a brief introduction to a new feature called Cluster Aware Updating (CAU), and in a later post I will take you through a live demo.
The good news is that in Server 2012 we have something called Cluster Aware Updating (CAU) that is meant to provide a reliable and automated method of patching clusters. When the feature is installed, instead of manually having to choose which updates the nodes need and applying them one at a time, you can allow the CAU service to determine the required updates by pointing to sources such as Windows Update Agent(WUA), Windows Server Update Services(WSUS), or even choose a location on a file share.
Tasks performed by CAU
So how does CAU orchestrate the installation of updates on a cluster?
- Moves the clustered roles off the node being updated
- Places the node being updated into maintenance mode
- Installs the required updates (this depends on the source that you choose)
- Performs a restart if necessary
- Brings the node out of maintenance mode
- Restores the clustered roles on the node
- Proceeds to the next node to complete the same process
Main Goals of CAU
- Minimize any disruption or downtime during the patching process
- Allow for a continuously available workload, which represents no impact to the service for users
- Orchestration updating all the nodes in the cluster, (while having no impact to service availability)
- Allow administrators to schedule updates for the nodes
Two Modes of CAU
There are two modes for CAU: self-updating mode as shown in Figure 1, and remote-updating mode as shown in Figure 2.
In self-updating mode the CAU role runs on one of the nodes, which acts as the update coordinator. The update coordinator is the node that ensures that the update process is applied throughout the cluster. The CAU role is also cluster-aware, which means that more than one node can become the CAU update coordinator – but only one node at a time can be an update coordinator.
Figure 1 – Self-Updating Mode
On the other hand, the remote updating mode allows for a remote machine running Server 2012 or Windows 8 to act as the CAU update coordinator. Utilizing this method is good for those that want to see the real-time progress of the updates, and for using CAU with windows 2012 Server Core.
Figure 2 – Remote-Updating Mode
CAU provides administrators with an easy-to-use GUI to determine which updates need to be installed, and when they should be installed.
CAU can be triggered using the GUI or you can utilize the included PowerShell cmdlets. As you see from the brief introduction above, CAU and many other features in Server 2012 strive to make the life of an administrator a lot easier.
Stay tuned for my next post where I will walk you through a live demo of CAU!
Posted by Tristan Kington, MSPFE Editor Trophy Dachshund