WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

1056 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

30.1 Overview

To avoid the loss of important assets, the administrator must back up the application-serving

environment and be able to recover that environment from a failure to a new environment. An

overview of this procedure includes the following actions:

 Backing up the product environment configuration:

– Administrative configuration files

– HTTP configuration (the documentation for the web server)

 Backing up the applications:

– Application deployment configuration files

 Backing up the application data:

– Business data

– Servlet session data

– Transaction data

30.2 Configuring for backup and restore

Most administrative configuration documents, with their saved settings, are represented in

WebSphere Application Serveras XML files. These configuration files and documents can be

located in profile_root/config. They must be backed up on a regular basis.

The procedure is as follows:

1. If the system is on a distributed environment, fully synchronize the administrative

configuration files. If the system is a stand-alone environment, proceed to the next step.

2. For backing up the system: Run the backupConfig command to back up the configuration

files.

3. For restoring the system: Run the restoreConfig command to restore the configuration

files.

4. For manual back up and restoration of the system: You can use the functions for exporting

and importing servers and the configuration archives for the profiles. More information,

refer the 30.2.3, “Exporting and importing a configuration archive” on page 1059

For more information about the WebSphere Application Serverconfiguration documents, refer

to the following website:

http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd

-dist&topic=rrun_rconfdoc_descriptions

30.2.1 Backing up a profile configuration

Use the backupConfig command to back up a profile configuration. Consider using this

command before making any significant configuration changes to your WebSphere

Application Serverenvironment.

Note: Restore the configuration only if the backup files are the same level of release,

including fixes, as the release to which you are restoring.

Chapter 30. System recovery 1057

You can run this command from the was_home/bin directory using the -profileName option to

specify the profile to back up. You can alternatively execute the command from the

profile_root/bin directory to back up only that specific profile.

The backupConfig command compresses the configuration files and stores the compressed

file in the current directory or a specified path. The compressed file can be restored using the

restoreConfig command. By default, backupConfig stops all servers in the configuration

before performing the backup. The syntax is shown in Example 30-1.

Example 30-1 backupConfig command

Usage: backupConfig [backup_file] [-nostop] [-quiet] [-logfile <filename>]

[-replacelog] [-trace] [-username <username>] [-password <password>] [-profileName

<profile>] [-help]

The backup_file parameter specifies the file where the backup is to be written. If you do not

specify a backup file name, a unique name is generated, and the file is stored in the working

directory. If you specify a backup file name with a directory name other than the current

directory, the specified directory must exist.

For more information about these command options and usage, refer to the information

center at the following website:

http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd

-mp&topic=rxml_backupconfig

Example 30-2 shows the use of the backupConfig command to back up the profile AppSrv01

configuration.

Example 30-2 backupConfig example

[root@saw211-RHEL2 bin]# pwd

/opt/IBM/WebSphere/AppServer/bin

[root@saw211-RHEL2 bin]# ./backupConfig.sh -profileName AppSrv01

ADMU0116I: Tool information is being logged in file

/home/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/backupConfig.log

ADMU0128I: Starting tool with the AppSrv01 profile

ADMU5001I: Backing up config directory

/home/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config to file

/home/opt/IBM/WebSphere/AppServer/bin/WebSphereConfig_2012-06-21_1.zip

ADMU0505I: Servers found in configuration:

ADMU0506I: Server name: server1

ADMU2010I: Stopping all server processes for node was85AppSrv01

Realm/Cell Name: <default>

Username: admin

Password:

ADMU0510I: Server server1 is now STOPPED

..................................................................................

..........................................................................

ADMU5002I: 812 files successfully backed up

30.2.2 Restoring a profile configuration

Use the restoreConfig command to restore a profile configuration from an archive that was

previously generated using backupConfig for that profile. The restoreConfig command