Re: Installing sp2 on active/passive cluster

I want to install CU4 Build 3200, but I didn't see any instructions with it.
At least I think I want to. Various people have said don't do it unless you
have to. One thing I want to correct on our system is that I am running
Enterprise Edition 64 bit SP2. I do not have the option to delete from first
level file folders for my maintenance task.

I really have no cluster experience. We are running an active/passive
cluster with DEV and PRD instances on it. I would like to do this to only
the DEV instance.

When I started the executable, it said there are running processes locking
files. To avoid a computer restart, end these. The are msftesql$DEV,
MSSQL$DEV, SQLAgent$DEV, resrcmon.exe twice, and SQLBrowser.

We cancelled out just because we weren't sure what to do.

Do you know if there are some instructions and how would I get my hands on
these?

Also, do you know where the delete from first level folders is fixed, so I
can havwe that option appear and check that box in the maintenance task?

Thanks much.

"Geoff N. Hiten" wrote:

Sounds like a pretty normal cluster install. :)

The Vista user provisioning tool only matters if you are running Vista with
UAC enabled. Otherwise it has no effect.

Not many people know that SQL 2005 is not named for its release year, but
for the number of reboots required to get a cluster up and running. :)


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"geek-y-guy" <noone@xxxxxxxxxxx> wrote in message
news:%23pz6b19kIHA.5084@xxxxxxxxxxxxxxxxxxxxxxx
thanks for the feedback...the install went well, except at the very end it
brought up the dialog about "adding Vista users to administrator role in
SQL" or something like that, and that step failed...I got a "server
unavailable" message when I tried to do it.

I then rebooted the active member, and the passive member

Is that something I need to worry about?

Also, after the first reboot, cluster service was hung on the active node.
I found a thread somewhere about this, and someone pointed to a technote
about updating MSDTC to allow network access. I did this on the passive
node and rebooted it, but that did not work...I was going to try it on the
active node when I decided to just reboot it once more...which I did.

After the reboot, the active node came back up normally, with all services
running, but now the passive node was dead in the cluster.

I then reversed what I had done on the passive node with MSDTC, rebooted,
and it came back up too (whew). No errors in the Applog either after the
second reboot.

So, it seems like a double re-boot was in order to get everything back to
normal?

"Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx> wrote in message
news:eGgO8W2kIHA.2396@xxxxxxxxxxxxxxxxxxxxxxx
Go ahead and run the install as written. You may have to hand-patch the
non-clustered components after the main install, but that is OK.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"geekyguy" <geeky@xxxxxxx> wrote in message
news:Oj60$40kIHA.1052@xxxxxxxxxxxxxxxxxxxxxxx
According to the sp2 readme:

3.2.5 Installing SQL Server 2005 SP2 on a Failover Cluster Instance
Note the following information before you install SP2 on a failover
cluster instance:
Do not stop the cluster service before you run the SP2 Setup program, or
while the installation program is running.
Do not end any running processes before you run the SP2 Setup program.
Do not take the SQL Server service off line before you run the SP2 Setup
program. The SP2 Setup program will stop and start the SQL Server
service.
Run the SP2 Setup program on the primary node of the failover cluster
instance.
You must restart all failover cluster nodes after SP2 is finished
installing.
Rolling upgrade is not supported for SP2.

I just want to make sure this is all I really have to do? I've read
elsewhere that non-cluster-aware SQL components like Workstation
Components/SMS will not be updated on the passive server unless I run
sp2 on that server after running it on the active node?

I want to get this right the first time!





.

Relevant Pages

  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Now, for the first problem, adding the 3rd node as a member of the cluster. ... You then installed a 2nd instance of SQL Server. ... DBC01 (Disks, SQL Server resources) ... Install RTM SS2K and designate the node membership. ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL Server 2005 Cluster Setup Quiz
    ... I did test and it did not install the client tools. ... http://www.clusterhelp.com - Cluster Training ... Microsoft SQL Server MVP ... Provide a template on how to read SQL Server 2005 setup log files. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Upgrade from SQL 2000 to SQL 2005 Problem in Active/Active Cluster Environment
    ... IIS is required by some SQL Server ... To install all SQL Server features, ... NODE2 is not the node in the cluster that I'm logged into or the ... node the SQL instance I want to upgrade is on. ...
    (microsoft.public.sqlserver)
  • Re: Setup cluster SQL server in SAN due to task scheduler
    ... I rebooted both nodes of the cluster ... Microsoft SQL Server 2005 Setup ... Setup failed to start on the remote machine. ... To install all SQL Server features, install IIS from Add or Remove Programs ...
    (microsoft.public.sqlserver.clustering)
  • Re: Installing sp2 on active/passive cluster
    ... You may have to hand-patch the non-clustered components after the main install, ... Installing SQL Server 2005 SP2 on a Failover Cluster Instance ... Do not stop the cluster service before you run the SP2 Setup program, or while the installation program is running. ...
    (microsoft.public.sqlserver.clustering)