BigFix - SQL Cluster Patching

BigFix - SQL Cluster Patching

Patching a SQL Server cluster is often the ultimate Sunday Scarier. Between managing node failovers, verifying service health, and the constant fear of a cluster-wide outage, it is a high-stakes manual marathon that costs IT teams their personal time.

It does not have to be this way.

In my latest article, I dive into how to leverage BigFix Server Automation to orchestrate the entire lifecycle of SQL cluster patching. By using out-of-the-box content, you can automate the heavy lifting:

  • Smart Sequencing: Automatically patching passive nodes first.
  • Safe Failovers: Moving cluster roles with precision.
  • Pre and Post Validation: Ensuring the cluster is healthy at every stage.

Automation is not just about speed; it is about reliability and getting your personal time back. Check out the guide below to see how you can transform a complex manual process into a repeatable, automated workflow.


As always refer to the official documentation here https://help.hcl-software.com/bigfix/11.0/lifecycle/Lifecycle/ServerAutomation/SAUsersGuide/Server_Automation_clusters/Patching%20Windows%202008%20clusters.html

 

 

First Step is to find Task ID 110 in the Server Automation Site and take action on the Servers you will using in the Automation Plan

 

Article content

Take Action

 

Article content

Target the Devices you will be using in the Automation Plans. (I I like to create a policy action so these scripts are always on these devices)

 

Article content

In the Console we will want to create a baseline of the patches we want to deploy.  Go to Tools Create a New Baseline

 

Article content

Select Add New Components

Article content


Add the Patches to the Baseline you would like to deploy during patching and Hit Ok and Hit OK again to Close your Baseline

 

Article content

Select the Server Automation Domain

 

Article content

Expand Automation and Select the Automation Plans Dashboard

Article content

Select the Create Button

 

Article content

Give the Plan a Name and select the site you want to add it to

 

Article content

Click on the settings Tab and Select Continue to Next Step on the Pending Restart

 

Article content

Select the Steps Tab and the Add Steps Button

 

Article content

Search for “Pre Patching Task For Non Hyper-V Clustered Microsoft Servers (Version 2008 R2 onwards)” and Select the Task ID 138 and Select Add

 

Article content

Select the Gear Icon

 

Article content

Search for the Machine you would like to Target first and add it to the selected Targets and Hit OK

 

Article content

Click on the Add Step Button

Article content


Search for “Make node unavailable as possible owner of resources in cluster” and select Task ID 340 and Select Add

Article content


Select the Gear Icon

Article content


Select the option to use the same target as step 1 and select OK.

 

Article content

Select Add Step

 

Article content

Search for “Resume Node (Windows 2008-2022)” and select Task ID 115 and select add

 

Article content

Select the Gears Icon

Article content


Select the same Target as Step 1 Option

 

Article content

 

Select Add Step

 

Article content

Search for patch or the baseline you would like to deploy.  I created a baseline called SQL Cluster Patches earlier that has the Patches I want to deploy to the SQL Servers and select Add

Article content


Select the Gear Icon

 

Article content

Select the same target as step 1 option and hit ok

 

Article content

Select Add Step

 

Article content

Search for Restart Endpoint and Wait for Restart to Complete and select Task ID 126 and Select Add

 

Article content

Select the Gear Icon

Article content


Select the use the same target as step 1 option and hit ok

 

Article content

 

Select Add Step

Article content


Search for “Make node available as possible owner of resources in cluster” and select Task ID 341 and hit Add

Article content


Select the Gear Icon

 

Article content

Select the use the same target as step 1 option and hit ok

 

Article content

Select Add Step

Article content


Search for “Post Patching task for Microsoft Server Clusters(Server 2008 R2 onwards including Hyper-V Clusters)” and select Task ID 129 and hit add

 

Article content

Select the Gear Icon

 

Article content

Select the use the same target as step 1 option and hit ok

 

Article content

Make rue Action1 is selected for the post patching step

 

Article content

Next you are going to repeat all of these steps for the different Nodes in the Cluster

Select Add Step

Article content


Search for “Pre Patching Task For Non Hyper-V Clustered Microsoft Servers (Version 2008 R2 onwards)” and Select the Task ID 138 and Hit Add

Article content


Select the Gear Icon

 

Article content

Select the Second Machine you would like to target and add it to your target list and hit OK

 

Article content

Select Add Step

Article content

Search for “Make node unavailable as possible owner of resources in cluster” and select Task ID 340 and Select Add

Article content

Select the Gear Icon

Article content

Select the option to use the same target as Step 8 and select OK.

 

Article content

 

 

Repeat these steps for the next 6 steps so that it mirrors the first 7 steps.  The only difference these steps will target the same machine as step 8

Once Complete you Plan will look like below.  The first 7 Steps will target the First Node and then the Second 7 Steps will Target the next Node

Article content


Select Save and now your plan is ready to test patching a SQL Cluster

 

Article content


To view or add a comment, sign in

More articles by Brad Sexton

Others also viewed

Explore content categories