How to rebuild a cluster node that is part of a Storage Foundation HA or InfoScale for Windows cluster

SECTION 1 - Backing up the Cluster Configuration

This section walks the user through backing up important information about the node and cluster. Some of these files will be required to complete the rebuilding process.  Back up these files and registry keys to a location that will not be affected by a complete uninstall and reinstall of Storage Foundation HA (SFW-HA) or InfoScale for Windows.

 

1. Export the following registry key from the node that will be rebuilt:
 

     HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base
  

2. If Exchange is involved, export the following key as well (if it exists**):
  

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\ExchConfig
    

      **Note: this key is no longer present in SFW HA 6.x for Exchange 2010 installations.

3. On the node that is going to be rebuilt, back up the following files:
  

%VCS_ROOT%\Cluster Server\conf\config\main.cf
 

%VCS_ROOT%\Cluster Server\conf\config\types.cf
 

%VCS_ROOT%\comms\llt\llttab.txt
 

%VCS_ROOT%\comms\llt\llthosts.txt
 

%VCS_ROOT%\comms\gab\gabtab.txt
  

Note: By default, %VCS_ROOT% is the equivalent of C:\Program Files\VERITAS
 

4.Back up the "lic" folder under following location:
  

C:\Program Files\Common Files\VERITAS Shared\vrtslic\lic
  

In 64bit operating systems the "lic" folder can be found here:

 

C:\Program Files (x86)\Common Files\Veritas Shared\vrtslic\lic

 

SECTION 2 - Removing the Node
 

1. Move any service groups to another node.
 

2. Remove the node that is going to be rebuilt from the System List of each service group. This can be done by performing the following steps: 

Note: Repeat the above steps for each service group as needed.
  

3. From a Windows command prompt, run the following commands on the node that is to be rebuilt: 

 

haconf -dump -makero
 

net stop llt /y 
 

4. Disable the following Windows services on the node that is to be rebuilt:
 

VERITAS Cluster Server Helper
 

VERITAS Command Server
 

VERITAS High Availability Engine
 

VERITAS VCSComm Startup
  

5. Delete the following files on the node that is to be rebuilt:
  

%VCS_ROOT%\Cluster Server\conf\config\main.cf
 

%VCS_ROOT%\comms\llt\llttab.txt
 

%VCS_ROOT%\comms\llt\llthosts.txt
 

%VCS_ROOT%\comms\gab\gabtab.txt
 

6. Delete the following registry keys on the node that is to be rebuilt:
 

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base\ClusterName
 

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base\ClusterID
 

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base\NodeID
  

7. If Veritas DMP (Dynamic MultiPathing) is being used, disable all but one path on the node that is to be rebuilt. 
  

8. From Add/Remove Programs uninstall "Storage Foundation HA for Windows (Server Components)" or "Veritas InfoScale ..." During the uninstall wizard, also select the removal of the "Client Components."
  

9. Reboot the node. 
  

SECTION 3 - Rebuilding the Node
  

1. Reinstall SFW-HA or InfoScale as normal on the node that is to be rebuilt. If needed, use the license keys that were previously backed up from the C:\Program Files\Common Files\VERITAS Shared\vrtslic\lic folder in "Section 1." 

 

2. Reboot the node.
 

3. Install any other hotfixes or patches that were previously installed. A reboot may or may not be necessary depending on the instructions for the individual patches.
 

Note: The version and patch level of SFW-HA/InfoScale should match the other nodes in the cluster before continuing.
 

4. If the node had previously been brought down to a single path, the other paths may be enabled again.
 

Warning: Before adding new paths, multipathing software should be enabled and the relevant hardware should be placed under the control of the multipathing software. Adding additional paths without configuring multipathing software can cause data corruption. If Veritas Dynamic Multipathing (DMP) is being used, this step can be performed by right-clicking on any existing path within VEA and removing the check from the "Exclude" option from the Array Settings dialog box.
 

5. Run the "Veritas Cluster Configuration Wizard" on the node that is to be rebuilt. Do not join this node to the existing cluster yet. Create a new cluster with this server as the only node.

Note: Select Yes when prompted to configure private link heart-beats on single node cluster.  This configures LLT, GAB, and VCSComm for auto-start.

 

6. From another node that is still in the original cluster (not the rebuilt node) run the following commands:
 

haconf -dump -makero
 

hastop -all -force
 

7. On the rebuilt node, run the following command:
 

hastop -all
 

net stop llt /y
 

8. If this is an Exchange cluster, restore the "ExchConfig" registry key to the rebuilt node. This key was previously backed up in "Section 1." The location of this key should be:
 

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\ExchConfig
  

9. Replace the "main.cf"  file on ALL nodes with the one that was backed up in "Section 1." The location of this file is:
 

%VCS_ROOT%\Cluster Server\conf\config\main.cf
 

10. On the rebuilt node only, replace the following files that had been previously backed up.
 

%VCS_ROOT%\comms\llt\llthosts.txt
 

%VCS_ROOT%\comms\llt\llttab.txt
 

%VCS_ROOT%\comms\gab\gabtab.txt
 

11. On the rebuilt node only, modify the following registry keys to match the other nodes in the cluster:
 

    HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base\ClusterName
 

    HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base\ClusterID
 

12. On the rebuilt node only, modify the NodeID registry key to match the value contained llthosts.txt:
 

    HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base\NodeID 
 

13. On the rebuilt node only, delete the following key if it exists:

  

    HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base\SingleNode

 

14. On any node, run the following command:
 

hastart -all
 

15. Run the following command to check the status of the nodes:
 

  hasys -state 
 

Note: If the cluster engine (had) fails to start, review engine_a.txt to determine the reason for the failure. In most cases, a had failure that occurs directly after rebuilding a node is the result of a minor mismatch between one of the registry keys or comms files that was backed up and restored. If errors are discovered, run net stop llt /y, followed by hastart to refresh the setting after making any changes. By default, engine_a.txt is located under the following path:
  

  %VCS_ROOT%\log\engine_a.txt