Guidelines for clustered deployments

If HCL WebSphere Portal is deployed in a clustered topology, both a primary node and additional nodes are running in a cluster. In this topology, there is no difference in database backup and restore because all cluster members use the same HCL WebSphere Portal databases. However, we need to consider some additional factors when we back up and recover the file system in a clustered deployment.

In a clustered deployment, adhere to these guidelines:

1. Follow the file system backup and recovery procedures on both the primary and additional nodes.

2. Back up the file system of the dmgr configuration, the master configuration repository for the cell, using one of the following methods:

   • Use the simple commands provided by IBM WebSphere Application Server: backupConfig and restoreConfig.

   • Use IBM Tivoli Storage Manager or other utility to back up the dmgr profile directory, where this configuration information resides.

3. When we restore HCL WebSphere Portal databases and file systems, make sure to restore the dmgr configuration at the same time the primary node and secondary node file systems are restored. Then, complete a node synchronization of both nodes using the dmgr WAS console. This step ensures the configuration is identical on both nodes and is consistent with the restored databases.

Parent Backup and restore