Cluster-aware SP

Hi,
I've read that installing a SQL Server SP is cluster-aware.
I'm just not sure what this means.
Does this mean that when running the setup on the active node (given 2
nodes), the setup will
- install files on the passive node (node2)
- failover to the other node (node2)
- install files on the first node (node1)
- failback to node1
or is this way off?
After installing the nodes probably needs a reboot. Running on node1;
- reboot node2
- when back up, failover to node2
- reboot node1
- when back up, failback to node1
'
Thanks for any enlightening.
Regards,audunj@.gmail.com wrote:
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>
SP will install files on both nodes but will ask for reatart only the
node you started sp, you need to restart the other one also (you'll
probably want to wait till the first one boots up)|||Cluster aware means acting appropriately in all cluster situations. If you
install a SP to an instance starting on the host node, it will update all
binaries on all accessable nodes AND run SQL update scripts. It will advise
you about rebooting both the local and remote node(s) but will not force a
reboot. If you run the SP from an node that does not currently host the
target instance, it will update local binaries only. Again, it will advise
but not force a reboot. This is covered in the Service Pack README file.
Hotfixes exhibit the same behavior. In some circumstances, SPs will not do
a binary-only local update and you will have to run the service pack again
on the entire instance.
Geoff N. Hiten
Microsoft SQL Server MVP
<audunj@.gmail.com> wrote in message
news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>|||Hi, thanx for the feedback.
How about availability during this SP installation? Will the server be
available for user connections as long as I do not reboot the nodes at
the same time? Or will I have to schedule with downtime?
TIA,
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:

> Cluster aware means acting appropriately in all cluster situations.
> If you install a SP to an instance starting on the host node, it will
> update all binaries on all accessable nodes AND run SQL update
> scripts. It will advise you about rebooting both the local and remote
> node(s) but will not force a reboot. If you run the SP from an node
> that does not currently host the target instance, it will update local
> binaries only. Again, it will advise but not force a reboot. This
> is covered in the Service Pack README file. Hotfixes exhibit the same
> behavior. In some circumstances, SPs will not do a binary-only local
> update and you will have to run the service pack again on the entire
> instance.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> <audunj@.gmail.com> wrote in message
> news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
>|||If you are applying the SP to an entire instance, that SQL server instance
will be unavailable. If you are updating local binaries only such as
replacing a failed node, then the instance will remain online.
Geoff N. Hiten
Microsoft SQL Server MVP
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns96718D200BF43gurbaohotmailcom@.12
9.250.171.67...
> Hi, thanx for the feedback.
> How about availability during this SP installation? Will the server be
> available for user connections as long as I do not reboot the nodes at
> the same time? Or will I have to schedule with downtime?
> TIA,
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
> news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
>
>