Feeds:
Posts
Comments

Archive for the ‘Cluster’ Category

1.Apply a service pack or hotfix SQL Server 2005 to a failover cluster instance

With SQL Server 2005, Microsoft tried to be helpful in enabling its installer to apply the service pack or hotfix automatically on the passive node(s) in a cluster. In my own experience, this has not worked out too well.

Very often, when the installer flagged the upgrade status of the service pack ot the hotfix as failure next to Database Service, the information I found in the log file was that attempt to patch the passive node had failed. You could scour the log files, google the internet, and/or open a Microsoft support case to troubleshoot the problem, rectify the root cause for failure to patch the passive node, and move on. But that may be a lengthy process, although sometimes you do not have a choice but to go through it.

In many cases, I have found the following simple solution to work well (the description assumes that we have node A and node B, and node A currently owns the SQL Server resource group):

  • Use Cluster Administrator to pause the passive node, i.e. node B
  • Re-apply the service pack or the hotfix on node A (i.e. the active node–the node that owns the SQL Server resource group). Because node B is paused, the installer will not try to help you out in applying the service pack or hotfix there. And re-applying the service pack or hotfix will usually succeed.
  • Un-pause node B.
  • If you need to reboot the patched node A, go ahead and reboot it. After node A has come back online, make sure that the SQL Server resource group is on node B. If not, move it there.
  • Pause node A with Cluster Administrator.
  • Apply the service pack or hotfix on node B. Again, this should typically succeed (unless there is some other issue).
  • Un-pause node A, and reboot node B, if necessary.

In essence, you may want to patch all the nodes manually yourself.

I’m not suggesting that this is a cure all for all the problems of patching a clustered SQL Server 2005. But it has worked quite well for me when the problem was a failed attempt to patch the passive node.

 

2.Apply a service pack or hotfix SQL Server 2008 to a failover cluster instance

Installing Service Pack SQL Server 2008 in failover cluster is very different than the SQL Server 2005 cluster failover.

With SQL Server 2005, when you start installing cluster service pack (or hotfix), it must be launched on the active node (node that hosts the instance). When installing the Setup will launch simultaneously  “remote silence” on all passive nodes. All nodes in the cluster containing the SQL Server instance are updated in the same time.

With SQL Server 2008, to reduce the downtime, we have revised the method of deployment. Now if you want to apply a service pack (or hotfix), you must install in first on the passive nodes. The passive nodes are updated before the active node.

Therefore, for your instance SQL Server 2008  in failover cluster, you must follow the scenario below for the application of Service Pack, Cumulative Update or Hotfix :

1.  Apply the hotfix on pasive node N2
2.  Reboot the passive node N2
3.  Failover on SQL resource : the passive node become the active node
4.  Apply the hotfix on the passive node N1
5.  Reboot the passive node N1

You can check the version of SQL server with the following query:

SELECT

SERVERPROPERTY(‘IsClustered’) as _1_Means_Clustered ,
SERVERPROPERTY(‘Edition’) as Edition ,
SERVERPROPERTY(‘ProductVersion’) as Version  ,
SERVERPROPERTY(‘ComputerNamePhysicalNetBIOS’) as ActiveNode

 

Links:-

http://sqlblog.com/blogs/linchi_shea/archive/2009/10/04/pause-the-passive-node-to-apply-sql2005-service-pack-or-hotfix.aspx

http://blogs.technet.com/b/mdegre/archive/2010/01/16/apply-a-sql-server-2008-service-pack-or-hotfix-to-a-failover-cluster-instance.aspx

Read Full Post »