 | |
Installing sp2 on active/passive cluster
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#41
 
| |||
| |||
|
Re: Installing sp2 on active/passive cluster -
04-07-2008
, 09:34 AM
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 (AT) nowhere (DOT) com> wrote in message news:%23pz6b19kIHA.5084 (AT) TK2MSFTNGP04 (DOT) phx.gbl... 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 (AT) gmail (DOT) com> wrote in message news:eGgO8W2kIHA.2396 (AT) TK2MSFTNGP02 (DOT) phx.gbl... 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 (AT) guy (DOT) com> wrote in message news:Oj60$40kIHA.1052 (AT) TK2MSFTNGP05 (DOT) phx.gbl... 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! |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.