Cluster with 1 server ok second not

Hi all,
The problem that we have:
We have a SQL cluster which contains 2 windows Adv servers, server X and Y
Y is the primary node, and on that node is a virtual SQL installed, X is the
secondary node, but it needs to be renstalled,
as there is a db running on the cluster, I wonder if it would have impact as
our db needs to stay online and how I need to do that?
Do I need to evict the second node and then renstall it, or just renstall
it?
Do I need to install the virtual SQL also on the second node or not?
Look in BOL for the topic 'Maintaining a failover cluster'. It has step by
step instructions on how to add a node to a running cluster. FYI, it can be
done without stopping the running instance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Colemont Bert" <colemont.bert@.pi.be> wrote in message
news:%23fxChwEKEHA.628@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> The problem that we have:
> We have a SQL cluster which contains 2 windows Adv servers, server X and Y
> Y is the primary node, and on that node is a virtual SQL installed, X is
the
> secondary node, but it needs to be renstalled,
> as there is a db running on the cluster, I wonder if it would have impact
as
> our db needs to stay online and how I need to do that?
> Do I need to evict the second node and then renstall it, or just
renstall
> it?
> Do I need to install the virtual SQL also on the second node or not?
>
|||Just be sure that you follow the BOL instructions BEFORE evicting the node
at the Windows level. And after you follow the BOL instructions to add the
node back (assuming you do so) apply the latest service pack/hotfix because
adding a node puts back the RTM version on the new node.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||When you apply the latest service pack/hotfix, does it require a down time? My understanding is applying SQL sp/hotfixes, you run it on a virtual server, not at individual nodes.
-- Cindy Gross (MSFT) wrote: --
Just be sure that you follow the BOL instructions BEFORE evicting the node
at the Windows level. And after you follow the BOL instructions to add the
node back (assuming you do so) apply the latest service pack/hotfix because
adding a node puts back the RTM version on the new node.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||It Depends.
The initial service pack or hotfix installation should be done at the node
that owns the resource. This will update all binaries and the share data
files. If you replace a node, you need to update the local binaries only.
That is when you run the installation from that node when it does NOT own
any group resources. The service pack installer will update the local
binaries only. This information is in the readme file for each service
pack.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Samm" <anonymous@.discussions.microsoft.com> wrote in message
news:0FEF5270-BEA9-41B0-B315-FE73B3D7532E@.microsoft.com...
> When you apply the latest service pack/hotfix, does it require a down
time? My understanding is applying SQL sp/hotfixes, you run it on a virtual
server, not at individual nodes.
> -- Cindy Gross (MSFT) wrote: --
> Just be sure that you follow the BOL instructions BEFORE evicting the
node
> at the Windows level. And after you follow the BOL instructions to
add the
> node back (assuming you do so) apply the latest service pack/hotfix
because
> adding a node puts back the RTM version on the new node.
> Cindy Gross, MCDBA, MCSE
> http://cindygross.tripod.com
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>