Restoring the Deployment Manager node

1. Reinstall IBM WAS Network Deployment V5.1 with the same parameters/features as used at the time of the initial system setup. The setup process will initially configure an empty cell without any federated nodes or appservers.

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

2. If the Deployment Manager process is running after installation, stop it using the stopManager command.

3. Restore the filesystem backup of the <WAS_HOME> directory.

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

4. Start the Deployment Manager using the startManager command.

Check the status of the nodes using the Administrative Console. You should find all previously defined nodes, Node Agents, appservers, enterprise applications, etc.

5. Optionally update the cell configuration with the latest changes since the backup snapshot was taken. Save and synchronize the configuration. Any changes made to the individual appservers will be lost because they are overwritten by the master configuration data from the Deployment Manage 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.