replace failed node without downtime? (sp1 question)

Is there a manual procedure whereby I could get a replacement node up to SP1
binaries without having to interrupt service by failing the cluster over
just to apply SP1 to the newly rebuilt node?
Hopefully I'm making sense - the node that went down was a passive node and
it's been rebuilt - but in order to get the binaries up to SP1 the only way
I know how is to fail the cluster to the new node just to get the SP1
binaries on it.
Thanks in advance!
Karl
Hi,
My understanding of your issue is: After adding a new node in SQL 2005
cluster instance, the SQL version on new node is RTM and old node is SP1
In such scenario, we have following two ways to apply SQL Sp1 for this SQL
2005 cluster.
1. Apply SP1 again on the active node (OLD node) and the new node
will be upgraded to SP3 as well.
2. Add registry Need_SP_Key on the passive node and install SQL
service pack 1on Passive node directly, In this way, the SP1 will only be
installed on Passive node.
Hope this helps.
Best regards,
Vincent Xu
Microsoft Online Partner Support
================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====
--[vbcol=seagreen]
SP1[vbcol=seagreen]
and[vbcol=seagreen]
way[vbcol=seagreen]
|||Yes, you understand what I'm trying to do. I have a couple of questions,
please.
If I try #1 on the old (already SP1) node - will it stop the SQL Service or
will it leave the active node online while it patches the passive node
remotely?
For #2 when I search for Need_SP_Key I only get SQL 2000 information and the
2005 BOL has nothing I can find about it. Sounds like the best option
though.
-Karl
"Vincent Xu [MSFT]" <v-xuwen@.online.microsoft.com> wrote in message
news:1EObEyf4GHA.2336@.TK2MSFTNGXA01.phx.gbl...
Hi,
My understanding of your issue is: After adding a new node in SQL 2005
cluster instance, the SQL version on new node is RTM and old node is SP1
In such scenario, we have following two ways to apply SQL Sp1 for this SQL
2005 cluster.
1. Apply SP1 again on the active node (OLD node) and the new node
will be upgraded to SP3 as well.
2. Add registry Need_SP_Key on the passive node and install SQL
service pack 1on Passive node directly, In this way, the SP1 will only be
installed on Passive node.
Hope this helps.
Best regards,
Vincent Xu
Microsoft Online Partner Support
================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====
--[vbcol=seagreen]
SP1[vbcol=seagreen]
and[vbcol=seagreen]
way[vbcol=seagreen]
|||Hi,
Found more information:
You can even install SP1 on node 2 directly:
- Verified that SP1 was successfully installed on Node1, we did that by
running
Select @.@.Version & physically checking the File Version property of
sqlservr.exe on
Node1 which is 2005.90.2047.0
- We made Node1 as a active node.
- Started installation on Node2.
Note: This time setup wont allow us to check the checkbox for instance in
"Feature
Selection" window, as Node1 (which is a active node) is already on SP1, so
we will
continue so we continued setup without it.
- Let it run for all products till setup got completed.
- Verified that SP1 was successfully installed on Node2, we did that by
running
Select @.@.Version & physically checking the File Version property of
sqlservr.exe on
Node2 which is 2005.90.2047.0
- Verified by failing over also.
Hope this helps.
Best regards,
Vincent Xu
Microsoft Online Partner Support
================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====
--[vbcol=seagreen]
<1EObEyf4GHA.2336@.TK2MSFTNGXA01.phx.gbl>[vbcol=seagreen]
or[vbcol=seagreen]
the[vbcol=seagreen]