Before you add a new node to the Resource Database, you should first back up the current configuration. The backup will be used later to help initialize the new node. It is also a safeguard. If the configuration process is unexpectedly interrupted by a panic or some other serious error, then you may need to restore the Resource Database from the backup.
Note
The configuration process itself should not cause any panics. However, if some non-PRIMECLUSTER software panics or if the SF causes a power cycle because of a CF cluster partition, then the Resource Database configuration process could be so severely impacted that a restoration from the backup would be needed.
Note
The restoration process requires all nodes in the cluster to be in single user mode.
Since the Resource Database is synchronized across all of its nodes, the backup can be done on any node in the cluster where the Resource Database is running. The steps for performing the backup are as follows:
Log onto any node where the Resource Database is running with system administrator authority.
Run the command clbackuprdb to back the Resource Database up to a file.
/etc/opt/FJSVcluster/bin/clbackuprdb -f file
For example:
# /etc/opt/FJSVcluster/bin/clbackuprdb -f /mydir/backup_rdb
clbackuprdb stores the Resource Database as a compressed tar file. Thus, in the above example, the Resource Database would be stored in /mydir/backup_rdb.tar.*. * represents the extension of the type of tar compression (Z or gz).
Make sure that you do not place the backup in a directory whose contents are automatically deleted upon reboot (for example, /tmp).
Note
The hardware configuration must not change between the time a backup is done and the time that the restore is done. If the hardware configuration changes, you will need to take another backup. Otherwise, the restored database would not match the actual hardware configuration, and new hardware resources would be ignored by the Resource Database.
