SSHARMA2
asked on
How do I fix mismatch SP2+Hotfix to SQL Cluster Node
Background: I have an Active-Passive Cluster environment hosting 24x7 critical hospital databases. I noticed that SP2+patch is missing on Passive node and planning to apply missing sp2+patch on Passive Node. This is a PRODUCTION and Critical so want to verify all my steps well in advance.
VIRTUAL
--------- Node-1------------ --------- Node-2------------
Windows 2003 Enterprise SP2 Windows 2003 Enterrpise SP2
SQL 2005 Enterprise, SP2+Patch SQL 2005 Enterprise, SP1
Active Passive
PLAN-A
1) Full Backups of all databases (System and Users).
2) Move groups on Node-2 using Cluster Administrator
3) Pause Node-1 using Cluster Administrator
4) Apply SP2 on Node-2. SP2 is cluster aware and this will search for Passive (Node-1 now) but it is in PAUSED so will complete only on NODE-2.
5) Continue for Patch in the same manner on Node-2.
6) Check Version on Node-2.
7) Resume-Node Node-1 using Cluster Administrator
8) Move groups on Node-1 using Cluster Administrator
PLAN-B
1) Full Backups of all databases (System and Users).
2) Move groups on Node-2 using Cluster Administrator
3) Apply SP2 on Node-2. SP2 is cluster aware and this will search for Passive (Node-1) and it is already up to date and will do nothing but will apply sp2 only on NODE-2.
4) Continue for Patch in the same manner on Node-2.
5) Check Version on Node-2.
6) Move groups on Node-1 using Cluster Administrator
7) Test results.
PLAN-C
1) Full Backups of all databases (System and Users).
2) Go to Node-1 (Active) and apply SP3. SP3 is cluster aware and will complete on Passive first and then active.
3) Check version on Active-Node-1.
4) Move groups on Node-2 using Cluster Administrator
5) Check version on Node-2 Active now.
6) I can remove SP3 only in add/remove program any time if anything goes wrong.
Questions:
1) Can I remove sp2 or patch only from Node-2 if anything goes wrong using add/remove program? I think this is not ROLLOVER as in SQL 2008.
2) Which plan is 100%?
3) Please add expert comments only.
Thank you very much in advance for everyone.
VIRTUAL
--------- Node-1------------ --------- Node-2------------
Windows 2003 Enterprise SP2 Windows 2003 Enterrpise SP2
SQL 2005 Enterprise, SP2+Patch SQL 2005 Enterprise, SP1
Active Passive
PLAN-A
1) Full Backups of all databases (System and Users).
2) Move groups on Node-2 using Cluster Administrator
3) Pause Node-1 using Cluster Administrator
4) Apply SP2 on Node-2. SP2 is cluster aware and this will search for Passive (Node-1 now) but it is in PAUSED so will complete only on NODE-2.
5) Continue for Patch in the same manner on Node-2.
6) Check Version on Node-2.
7) Resume-Node Node-1 using Cluster Administrator
8) Move groups on Node-1 using Cluster Administrator
PLAN-B
1) Full Backups of all databases (System and Users).
2) Move groups on Node-2 using Cluster Administrator
3) Apply SP2 on Node-2. SP2 is cluster aware and this will search for Passive (Node-1) and it is already up to date and will do nothing but will apply sp2 only on NODE-2.
4) Continue for Patch in the same manner on Node-2.
5) Check Version on Node-2.
6) Move groups on Node-1 using Cluster Administrator
7) Test results.
PLAN-C
1) Full Backups of all databases (System and Users).
2) Go to Node-1 (Active) and apply SP3. SP3 is cluster aware and will complete on Passive first and then active.
3) Check version on Active-Node-1.
4) Move groups on Node-2 using Cluster Administrator
5) Check version on Node-2 Active now.
6) I can remove SP3 only in add/remove program any time if anything goes wrong.
Questions:
1) Can I remove sp2 or patch only from Node-2 if anything goes wrong using add/remove program? I think this is not ROLLOVER as in SQL 2008.
2) Which plan is 100%?
3) Please add expert comments only.
Thank you very much in advance for everyone.
ASKER
Hi - Genius
I tested in the following way
a) I ran the following query when I was connected to Node-1 ( It gave me SP2+Patch info);
SELECT SERVERPROPERTY('productver sion') AS VersionNumber,
SERVERPROPERTY ('productlevel') AS ProductLevel,
SERVERPROPERTY ('edition') AS Edition
b) Failover on Node-2 and ran same query and got SP1 info.
I tested in the following way
a) I ran the following query when I was connected to Node-1 ( It gave me SP2+Patch info);
SELECT SERVERPROPERTY('productver
SERVERPROPERTY ('productlevel') AS ProductLevel,
SERVERPROPERTY ('edition') AS Edition
b) Failover on Node-2 and ran same query and got SP1 info.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi - angellll,
Thanks for your prompt reply.
I know SP3 is perfect solution but considering overall situation I will concentrate on Workaround 'Method 1' (http://support.microsoft.com/kb/934749): Sounds like my PLAN-B.
a) Fail over to the new node.
b) Pause other nodes by using Cluster Administrator.
c) Install SQL Server 2005 SP2 on the new node.
d) Apply SQL Server 2005 SP2 Cumulative Update 6 and the appropriate hotfixes as applicable to the scenario on the new node.
e) Start the nodes that you paused
Thanks for your prompt reply.
I know SP3 is perfect solution but considering overall situation I will concentrate on Workaround 'Method 1' (http://support.microsoft.com/kb/934749): Sounds like my PLAN-B.
a) Fail over to the new node.
b) Pause other nodes by using Cluster Administrator.
c) Install SQL Server 2005 SP2 on the new node.
d) Apply SQL Server 2005 SP2 Cumulative Update 6 and the appropriate hotfixes as applicable to the scenario on the new node.
e) Start the nodes that you paused
yes, except that you planned to play safe with:
1) Full Backups of all databases (System and Users).
which is really good!
1) Full Backups of all databases (System and Users).
which is really good!
ASKER
We have next week schedule to complete this task and I will post my comments after that. Thanks.
ASKER
This has been rescheduled and will take place after three weeks.
ASKER
This has been completed successfully. Thanks for suggestion and verification.
ASKER
This was nice experience that we can ask/verify solution before apply on PROD.
patching a individual node should not work?
unless you only patched a client tools?
>I noticed that SP2+patch is missing on Passive node
can you clarify how you identified that?