Adding new nodex to a cluster or replace a node in a cluster.
There are several bugs in the microsoft cluster when comming to adding a new node or replace an existing node. Among them are: – Cluster group will not have any prefered owners, this must be added after installation – Installation requires a cd key, even though the installation is silent and the key is stored in the registry.
To avoid this problem, add the key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession Manager] add Dword:”SafeDllSearchMode” value should be 0 to the registry.
This must be done on both nodes! – You must be logged in as the cluster/ sql server account. If not the installation will fail. You can chage user during installation but then the cluster can not verify the accounts rights. – After installation all sql server resources will need to be manualy edited for prefered owners.
They will not be able to move to the other node until this is done. – Most sql server instances will have the default port of 1433 or 0 instead of their correct port numbers.
The original server will still have the correct port numbers so you can go copy them from there. – MSDTC must be configured on the new node to accept network connections. If not, sql server will not go on-line on the new service. This must be manualy changed ont he new node. – Installing sp4 on only the new node is not possible in this scenario, the selection will be greayed out.
You have to install a full sp4 on the whole cluster instance, also the one already patched. After this hotfixes needs to be reapplied.
2. How to add a new node to a sql cluster.
After serveral days work with a failing cluster at XYZ i have learnd the hard way how to get around the problems we will have when installing a new node to a cluster. This is very important to know since it is part of our disaster recovery work.
This is how to do it, let do it now.
Background. We had to reinstall one of the nodes in the cluster. One server where evicted and reinstalled. After reinstallation we open up cluster administrator from the working node. Just right click on the cluster and choose add node. Follow instructions and your node will be added. This work will be done by the SAS team in normal cases. When they are done our work starts:
First: Make sure that each cluster resource for sql server ( ip, networkname, sql, gent and fulltext) only have one one possible owner(right click on the resource and click properties)
Second: add this to the registry on both nodes:
add Dword:”SafeDllSearchMode” value should be 0
Now you can start to install: From the working, start the set up program of sql server 2000 enterprise edition. On the Welcome screen of the Microsoft SQL Server Installation Wizard, click Next.
On the Computer Name screen, click Virtual Server and specify the virtual server to which you want to add a node. Click Next.
On the Installation Selection screen, click Advanced options. Click Next.
On the Advanced Options screen, click Maintain a virtual server for failover clustering. Click Next.
On the Failover Clustering screen, click Next.
You do not need to enter an IP address.
On the Cluster Management screen, select the node and click Add.
If the node is listed as unavailable, you must modify the disk resources in the cluster group of the virtual server so the disk is available for the node you want to add to the Microsoft SQL Server configuration. Click Next.
On the Remote Information screen, enter login credentials for the remote cluster node that has administrator privileges on the remote node of the cluster. Click Next.
On the Setup Complete screen, click Finish.
On the new node there will probably be this registry key:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server80Need_SP_Key
Remove it completetely. If not, you will no tbe able to reinstall sp4.
Install sp4 and all hotfixes
Set possible owners to both nodes on all resources move cluster group to other node and make usre everythng is working.
Now you are done:-)
Service packs and hotfixes needs to be installed to both nodes!
When installing a hotfix or a service pack in a cluster it will be installed on both nodes.
This is however not the fact with SSIS, Books online, management studio and other softwares not cluster aware. They all need to be installed on both nodes separately. If we need to apply e.g. a hotfix to SSIS, then we need to do this on both nodes and not just the active one. In short, all services not fully cluster aware needs to be manualy updated!
Khan sql dba – mcitp