Add a new SQL2000 node

Based on the other threads I've read in the group, I'd like to confirm
the steps needed to perform to add a third node to a cluster that has
been running for a while on 2 nodes...
After adding the new node to the cluster, for each instance in the
cluster (assume: each instance is its own cluster group):
1) Run SQL2000 setup from CD on one of the older nodes; instruct setup
to add the new node as a target for failover.
2) Move the cluster group, making it active on the new node.
3) Install SQL2000 SP4 to the instance from the new node.
Am I missing any steps? Are there additional hotfixes (post-SP4) that
should be installed?
The current (active/active) cluster is running on Win2003 ENT SP1, while
the new node already has Win2003 ENT R2 SP2. The plan is to upgrade the
older hosts to the same rev after the new node is up. Is this workable?
To minimize downtime, you don't have to move any groups to apply SP4.
Rather, from the new node, apply SP4. After that, move the SQL group and
apply the post-SP4 hotfix.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"horseradish" <millardjk@.gmail.com> wrote in message
news:O5L1VrQjHHA.4132@.TK2MSFTNGP05.phx.gbl...
Based on the other threads I've read in the group, I'd like to confirm
the steps needed to perform to add a third node to a cluster that has
been running for a while on 2 nodes...
After adding the new node to the cluster, for each instance in the
cluster (assume: each instance is its own cluster group):
1) Run SQL2000 setup from CD on one of the older nodes; instruct setup
to add the new node as a target for failover.
2) Move the cluster group, making it active on the new node.
3) Install SQL2000 SP4 to the instance from the new node.
Am I missing any steps? Are there additional hotfixes (post-SP4) that
should be installed?
The current (active/active) cluster is running on Win2003 ENT SP1, while
the new node already has Win2003 ENT R2 SP2. The plan is to upgrade the
older hosts to the same rev after the new node is up. Is this workable?
|||There's no need to move the cluster group unless you want to test it will
correctly will startup.
For the SP4. If i Remember well Setup will detect that there's only one node
missing for the SP4 binnaries and will update only that node without
affecting the others.
Hope this helps.
Regards.
FR.
"horseradish" wrote:

> Based on the other threads I've read in the group, I'd like to confirm
> the steps needed to perform to add a third node to a cluster that has
> been running for a while on 2 nodes...
> After adding the new node to the cluster, for each instance in the
> cluster (assume: each instance is its own cluster group):
> 1) Run SQL2000 setup from CD on one of the older nodes; instruct setup
> to add the new node as a target for failover.
> 2) Move the cluster group, making it active on the new node.
> 3) Install SQL2000 SP4 to the instance from the new node.
> Am I missing any steps? Are there additional hotfixes (post-SP4) that
> should be installed?
> The current (active/active) cluster is running on Win2003 ENT SP1, while
> the new node already has Win2003 ENT R2 SP2. The plan is to upgrade the
> older hosts to the same rev after the new node is up. Is this workable?
>
|||Tom Moreau wrote:
> To minimize downtime, you don't have to move any groups to apply SP4.
> Rather, from the new node, apply SP4. After that, move the SQL group and
> apply the post-SP4 hotfix.
>
Based on other things I've seen, it appears that I should be able to add
two nodes (my ultimate plan is to get to 3 nodes using two new and one
current host) to the SQL cluster simultaneously, either when installing
SQL2K RTM _or_ SP4.
Then, once I have my 4-node cluster running, I can uninstall from SQL
and MSCS the one node I wish to remove.
Or will I have to fully install & patch the first new node before I can
repeat with the second?
|||You're probably safer to patch as you go. What if there was a failover in
the middle of what you're doing? It's best to have new nodes like the old
one as soon as you can.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"horseradish" <millardjk@.gmail.com> wrote in message
news:Otdi2JojHHA.4896@.TK2MSFTNGP02.phx.gbl...
Tom Moreau wrote:
> To minimize downtime, you don't have to move any groups to apply SP4.
> Rather, from the new node, apply SP4. After that, move the SQL group and
> apply the post-SP4 hotfix.
>
Based on other things I've seen, it appears that I should be able to add
two nodes (my ultimate plan is to get to 3 nodes using two new and one
current host) to the SQL cluster simultaneously, either when installing
SQL2K RTM _or_ SP4.
Then, once I have my 4-node cluster running, I can uninstall from SQL
and MSCS the one node I wish to remove.
Or will I have to fully install & patch the first new node before I can
repeat with the second?
|||Tom Moreau wrote:
> You're probably safer to patch as you go. What if there was a failover in
> the middle of what you're doing? It's best to have new nodes like the old
> one as soon as you can.
>
Thanks! The safer way is the right way for this implementation...
|||Tom Moreau wrote:
> To minimize downtime, you don't have to move any groups to apply SP4.
> Rather, from the new node, apply SP4. After that, move the SQL group and
> apply the post-SP4 hotfix.
>
Which HF is 'the post-SP4 hotfix'?
|||Check out:
http://aspfaq.com/SQL2000Builds.asp
The hotfix to correct the AWE issue is build 8.00.2040. There have been
subsequent fixes, which are cumulative, so you could apply a later one
instead.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"horseradish" <millardjk@.gmail.com> wrote in message
news:%23rObwnioHHA.4412@.TK2MSFTNGP02.phx.gbl...
Tom Moreau wrote:
> To minimize downtime, you don't have to move any groups to apply SP4.
> Rather, from the new node, apply SP4. After that, move the SQL group and
> apply the post-SP4 hotfix.
>
Which HF is 'the post-SP4 hotfix'?