Restoring a WAS Base node

Because all configuration data is kept in the master repository on the Deployment Manager node, the following procedure is fairly easy due to IBM WAS's centralized configuration replication mechanism:

1. Reinstall IBM WAS Base V5.1 (and IBM HTTP Server if collocated on the same system) with the same parameters/features as used at the time of the initial system setup.

The node name of the failed node can be retrieved from the WebSphere Administrative Console by expanding System Administration and clicking Nodes (see Figure A-3).

For information on installing WAS V5.0 and higher and IBM HTTP Server, refer to redbook IBM WAS V5.0 System Management and Configuration: WebSphere Handbook Series, SG24-6195 or to the WebSphere V5.1 InfoCenter.

2. Restore the filesystem backup into the <WAS_HOME> directory.

Important: Remove (or rename) the <WAS_HOME> directory before restoring the backup. Otherwise the backup results in a repository containing data of the initial, default and the newly restored configuration.

3. Perform a full node synchronization using the syncNode command. The Node Agent contacts the Deployment Manager and performs a full repository synchronization. When it terminates, the node will have the latest configuration data.

For detailed instructions on how to use syncNode, refer to Appendix A.7 in IBM WAS V5.0 System Management and Configuration: WebSphere Handbook Series, SG24-6195 or to the WebSphere V5.1 InfoCenter.

4. Start the Node Agent using the startNode command.

5. Start the appserver or cluster member on the newly restored node.

  Prev | Home | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.