September 26, 2008 at 7:26 am
I inherited a 2-node cluster (Win2003R2 x64, SQL2005EE x64 sp2) with a problem to fix.
Node1 has all of these showing as installed, Node2 only shows the basic installed features (engine, agent, etc). I have to have all these features available on Node2, so I'm looking to get them installed. I'm looking to use the SQL install and just add the features.
1. Does Node2 have to be active to do the feature install, or can it stay passive?
2. I think sp2 will need to be reapplied after the feature install. I'd like confirmation on this.
3. What are the implications to Node1?
September 26, 2008 at 8:33 am
Check windows/sql documentation, it's pretty clear about this situation, for example see this fragment from MSSQL 2K5 CU9:
Cumulative Update 9:
Failover Cluster Installation
The following information applies only to SQL Server 2005 components that are part of a failover cluster.
To install the service pack on a failover cluster:
To ensure that SQL Server 2005 SP2 will be installed on all nodes of a failover cluster instance, verify that the TASK Scheduler is running on all passive nodes of your failover cluster instance.
If any resources have been added that have dependencies on SQL Server resources, those dependencies must either be removed or taken offline before you install SQL Server 2005 SP2. If you do not remove the dependencies, the installation of SP2 will take those resources offline.
Note:
When a clustered resource is taken offline, all dependent resources are also taken offline by the cluster service.
Run the SQL Server 2005 SP2 executable package file from the active node that owns the group containing the failover cluster instance that you plan to upgrade. This installs the service pack files on all nodes in the failover cluster. You cannot install SP2 from any passive nodes in the failover cluster.
On the Feature Selection page of the SQL Server 2005 SP2 Setup Wizard, select the failover cluster instance that you plan to upgrade. Setup will prompt you for the login credentials that are used to connect to other nodes in the cluster.
Note:
Keep all nodes of the cluster online during Setup. This ensures that the upgrade is applied to each cluster node.
If you removed dependencies or took resources offline in step 1, restore the dependencies, or bring the resources online.
Note:
Setup might require you to restart the failover cluster nodes. This restart replaces the files that were in use during Setup.
Rebuild a SQL Server 2005 SP2 Failover Cluster Node
If you must rebuild a node in the failover cluster after SP2 has been applied, perform the following steps:
Rebuild the node in the failover cluster. For more information about rebuilding a node, see "How to: Recover from Failover Cluster Failure in Scenario 1" in SQL Server Books Online.
Run the original SQL Server 2005 Setup program to restore the node to the failover cluster.
Run SQL Server 2005 SP2 Setup on the node that you have added.
Wilfred
The best things in life are the simple things
September 26, 2008 at 11:48 am
It seems only the clustered resources is installed on node 2. You can run the client setup on node 2 and install the non-clustered features you like (Management Tools,SSIS etc). After installation you should apply SP2. If you're running active/passive you can reboot node2 when it's not in use. Should work without reboot but the locked files warning (in SP2 installer) will tell you.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply