After you have backed up the currently running Resource Database, you will need to reconfigure the database to recognize the new node. Before you do the reconfiguration, however, you need to perform some initial steps.
After these initial steps, you should reconfigure the Resource Database. This is done by running the clsetup command on any of the nodes which is currently running the Resource Database. Since the Resource Database is synchronized across all of its nodes, the reconfiguration takes effect on all nodes. The steps are as follows:
Log in to any node where the Resource Database is running. Log in with system administrator authority.
If this node is not the same one where you made the backup, then copy the backup to this node. Then run the clsetup command with the -a and -g options to reconfigure the database. The configuration information of the resource database that is generated after the execution of clsetup command is also used in the configuration of new node of the resource database. That is why for the --goption, do not specify the directory (eg:/tmp) that is automatically deleted during the node restart-up.
# /etc/opt/FJSVcluster/bin/clsetup -a cfname -g filecfname is the CF name of the new node to be added, and file is the name of the backup file without the .tar.* suffix. * represents the extension of the type of tar compression (Z or gz).
For example, suppose that you want to add a new node whose CF name is fuji4 to a cluster.
If the backup file on an existing node is named /mydir/rdb.tar.Z, then the following command would cause the Resource Database to be configured for the new node:
# cd /etc/opt/FJSVcluster/bin/ # ./clsetup -a fuji -g /mydir/rdb.tar.Z
If clsetup is successful, then you should immediately make a new backup of the Resource Database. This backup will include the new node in it. Be sure to save the backup to a place where it will not be lost upon a system reboot.
If an unexpected failure such as a panic occurs, then you may need to restore the Resource Database from an earlier backup. See "3.6.5 Restoring the Resource Database" for details.
To verify if the reconfiguration was successful, run the clgettree command. Make sure that the new node is displayed in the output for that command. If it is not present, then recheck the CIP configuration to see if it omitted the new node. If the CIP configuration is in error, then you will need to do the following to recover:
Correct the CIP configuration on all nodes. Make sure that CIP is running with the new configuration on all nodes.
Restore the Resource Database from backup.
Rerun the clsetup command to reconfigure the Resource Database.