Apply a service pack or hotfix SQL Server 2008 to a failover cluster instance
Apply a service pack or patch SQL Server 2008 in a clustered environment
Step 1 : Validation wizard
Step 2 : Pre-check
Step 3 : Installation of the first node
Step 4 : Add a new node
Step 5: Apply a service pack or hotfix on a SQL cluster
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:
Appliquer un service pack ou correctif SQL Server 2008 dans un environnement en cluster
Etape 1 : Validation wizard
Etape 2 : Pré- requis
Etape 3 : Installation du premier noeud
Etape 4 : Ajouter un nouveau noeud
Etape 5 : Appliquer un service pack ou correctif sur un cluster SQL
L’installation de Service Pack sur SQL server 2008 en cluster est très différente de la version SQL server 2005 en cluster.
Avec SQL server 2005, lorsque vous lancez l’installation en cluster d’un service pack (ou hotfix), celui-ci doit être lancé sur le nœud actif (nœud qui héberge l’instance). Au moment de l’installation le Setup va lancer simultanément des installations « remote silence » sur tous les nœuds passifs. Tous les nœuds du cluster contenant l’instance SQL Server sont donc mis à jours tous en même temps.
Avec SQL server 2008, afin de réduire les temps d’indisponibilité de l’instance, nous avons revu le mode de déploiement. Désormais lorsque vous souhaitez appliquer un service pack (ou hotfix), vous devez les installer sur les nœuds passifs. Les nœuds passifs sont donc mis à jours avant le nœud actif.
Par conséquent, pour votre instance SQL server 2008 en cluster, vous devez suivre le scénario suivant pour l’application du Service Pack, Cumulative Update ou Hotfix :
1. Application du hotfix sur le nœud passif N2
2. Reboot du nœud passif N2
3. Basculement du cluster : le nœud passif devient le nœud actif
4. Application du hotfix sur le nœud passif N1
5. Reboot du nœud passif N1
Vous pouvez ensuite vérifier la version de SQL server avec la requête ci-dessous :
Aplicar un service pack o un parche de SQL Server 2008 en un entorno agrupado
Paso 1 : Validation wizard
Paso 2 : Pre- requisitos
Paso 3 : Instalación del primer nodo
Paso 4 : Agregar un nuevo nodo
Paso 5 : Aplicar un service pack o un parche en un SQL cluster
Instalación de Service Pack de SQL Server 2008 en clúster es muy diferente que SQL Server 2005 en clúster.
Con SQL Server 2005 cuando se inicia la instalación en clúster de un Service Pack (o revisión), se debe lanzar en el nodo activo (nodo que aloja la instancia). Cuando el programa de instalación, el setup se iniciará al mismo tiempo las instalaciones en modo silencio en todos los nodos pasivos. Todos los nodos del clúster que contiene la instancia de SQL Server se actualiza cada vez que el mismo tiempo.
Con SQL Server 2008 para reducir el tiempo de inactividad de una instancia , hemos revisado el método de despliegue. Ahora bien, si desea aplicar un service pack (o revisión), debe instalar en los nodos pasivos. Los nodos pasivos se actualizan antes de que el nodo activo.
Por lo tanto, para una instancia de SQL Server 2008 de clúster de conmutación por error, debe seguir el siguiente escenario para la aplicación del Service Pack, Cumulative Update o Hotfix :
1. Aplique la revisión en el nodo pasiva N2
2. Reinicie el pasivo nodo N2
3. Cambiar de recurso de SQL: el nodo pasivo convertido en el nodo activo
4. Aplique la revisión en el nodo pasiva N1
5. Reinicie el pasivo nodo N1
Puede comprobar la versión de SQL Server con la siguiente consulta:
SELECT
SERVERPROPERTY('IsClustered') as _1_Means_Clustered ,
SERVERPROPERTY('Edition') as Edition ,
SERVERPROPERTY('ProductVersion') as Version ,
SERVERPROPERTY('ComputerNamePhysicalNetBIOS') as ActiveNode
SQL Server 2008 failover cluster rolling patch and service pack process
https://support.microsoft.com/kb/958734
How to update or slipstream an installation of SQL Server 2008
https://support.microsoft.com/kb/955392
Michel Degremont | Microsoft EMEA
Product Support Services Developer - SQL Server Core Engineer |
Comments
Anonymous
January 01, 2003
Does anyone know how internally services will be updated? I mean to say, if we are installing Service Pack 3 on SQL server 2008 Passive node (Without removing that node from cluster according to this article), what would be installed on that passive node. As per I know there won't be any SQL server services to update on that node, eventhough if we would have client tool, it should update only new features related to the installed tools. So how would the services will be updated? I am comparing it to SQL 2K5, that when we do update on active node, it will update the database engine service on that node.So, SQL 2k8 come up with separate update for database engine service irrelevant of nodes? That means if we failover to Passive, DB Engine or Server automatically runs under SP3? and similar thing we can do with Active? Please clarify. Thanks, ParthikAnonymous
January 01, 2003
Hi Mark, SQL Server Failover is an Active/Passive cluster. When someone says Active/active for SQL Server, that means 2 instances are hosted by the cluster. First instance is on the fist node, and the second one, on the second node.Anonymous
January 01, 2003
Hi SQL 2005 and 2008 are really different regarding the cluster installation. With SQL 2005, the setup will install in silence on all nodes. But with 2008 you have to run the SP on each node. The SP will first update the binaries files. Then when you will failover on the passive node, during the startup a script will be run. If you have a look inside SQL Serve error log, you will see some information about this script. I confirm you that you don’t need to remove any node during the setup of SP. Cheers, Michel.Anonymous
January 01, 2003
Thak you Michel - simple and to the point.Anonymous
October 11, 2010
Thanks a Ton for simplifying the process of Installing the SQL 2008 Service Pack, since it is different in both 2005 and 2008. I now understand the difference!Anonymous
May 09, 2011
Hi Michel, thanks for the information, 2008 seems much more simpler, but I just wanted to check one thing - do you have to make any cluster modification to the cluster, i.e. remove the passive node from the activepassive fail-over cluster and the list of possible network resource owners, before you patch it?Anonymous
November 21, 2011
What if it is and ActiveActive cluster?Anonymous
January 30, 2012
Attached the offical installation procedure: support.microsoft.com/.../958734Anonymous
August 21, 2013
Lovely Document, cleared the Setup idea