Restoring the application server configuration from a backup

If you configured a stand-alone application server instance for data collection either manually or with the configuration or migration utility and the application server fails to start, you must restore the application server configuration from a backup. If you did not create a backup, contact IBM® Support.

About this task

In a Network Deployment environment, if you configured an application server instance for data collection manually or with the configuration or migration utility and the application server fails to start, you have the following options:

You can restore the application server configuration from a backup configuration. If you did not create a backup, contact IBM Support.
You can manually unconfigure the data collector. The Deployment Manager and the Node Agent on the application server must be running. For more information, see Manually removing data collector configuration from an application server instance.

This section applies only to the Windows, UNIX, and Linux® operating systems.

Procedure

To apply the backup configuration by using the restoreConfig command, use one of the following procedures:

In a non-Network Deployment environment, complete the following steps:
1. Locate your backup configuration file.
  
  The default directory is dc_home/data. If several backup files are present, check the modification date and time of the file. It must be the date and time of the failed configuration. If you did not complete any other data collector configurations on the same host after the failed one, use the most recent file in the directory.
2. Stop all instances of the application server.
3. Run the restoreConfig command from the appserver_home/profiles/profile_name/bin directory.
  The command syntax is as follows:
  - restoreConfig.bat full_path_to_backup_file
  - ./restoreConfig.sh full_path_to_backup_file
  For more information about the arguments of the restoreConfig command, see the topic in WebSphere Application Server Knowledge Center.
4. Start the instances of the application server again.
In a Network Deployment environment, complete the following steps:
1. Locate your backup configuration file.
  
  The default directory is dc_home/data. If several backup files are present, check the modification date and time of the file; it must be the date and time of the failed configuration. If you did not complete any other data collector configurations on the same host after the failed one, use the most recent file in the directory.
2. Stop all instances of the application server.
3. Create a temporary directory in any convenient path (temp_directory). On a UNIX or Linux system, create it under the /tmp directory.
4. Run the restoreConfig command from the appserver_home/profiles/profile_name/bin directory.
  The command syntax is as follows:
  - restoreConfig.bat full_path_to_backup_file
  - ./restoreConfig.sh full_path_to_backup_file
  The restoreConfig command restores the original application server configuration to the temporary directory.
5. Copy the server.xml, variables.xml, and pmi-config.xml files from temporary directory to the Deployment Manager system.
  - Source directory: temp_directory/restored_configuration_home/cells/cell_name/nodes/node_name/servers/server_name
  - Target directory: appserver_home/profiles/profile_name/config/cells/cell_name/nodes/node_name/servers/server_name
6. Complete a node sync from the Deployment Manager administrative console for the node.
7. In the Deployment Manager administrative console, save changes to the master configuration.
8. Start the instances of the application server.