Guidelines for clustered deployments
If IBM 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 WebSphere Portal databases. However, you need to consider some additional factors when backing up and recovering the file system in a clustered deployment.
In a clustered deployment, adhere to these guidelines:
- Follow the file system backup and recovery procedures on both the primary and additional nodes.
- Back up the file system of the Deployment Manager configuration, the master configuration repository for the cell, using one of the following methods:
- Use the simple commands provided by IBM WAS: backupConfig and restoreConfig.
- Use IBM Tivoli Storage Manager or other utility to back up the Deployment Manager profile directory, where this configuration information resides.
- When restoring WebSphere Portal databases and file systems, make sure to restore the Deployment Manager configuration at the same time that the primary node and secondary node file systems are restored. Then perform a node synchronization of both nodes using the Deployment Manager Administration Console. This step ensures that the configuration is identical on both nodes and is consistent with the restored databases.
Parent
Backup and restore