Backup Websphere Configuration using backupconfig.sh

The following options are available for the backupConfig command:

-nostop

Tells the backupConfig command not to stop the servers before backing up the configuration

-quiet

Suppresses the progress information that the backupConfig command prints in normal mode

-logfile file_name

Specifies the location of the log file to which trace information is writtenBy default, the log file is named backupConfig.log and is created in the logs directory

-profileName profile_name

Defines the profile of the application server process in a multi-profile installationThe -profileName option is not required for running in a single-profile environment. The default for this option is the default profile.

-replacelog

Replaces the log file instead of appending to the current log

-trace

Generates trace information into the log file for debugging purposes

-username user_name

Specifies the user name for authentication if security is enabled in the server; acts the same as the -user option

-user user_name

Specifies the user name for authentication if security is enabled in the server; acts the same as the -username option

-password password

Specifies the password for authentication if security is enabled in the server

-help

Prints a usage statement

-?

Prints a usage statement

[was61@Server1 bin]$ ./restoreConfig.sh
Usage: restoreConfig backup_file [-location restore_location] [-quiet]
[-nostop] [-nowait] [-logfile <filename>] [-replacelog] [-trace]
[-username <username>] [-password <password>] [-profileName
<profile>] [-help]

[was61@Server1 bin]$ pwd
/opt/IBM/WebSphere/AppServer/profiles/Profile01/dmgr/bin
[was61@Server1 bin]$ ./restoreConfig.sh /opt/IBM/WebSphere/AppServer/profiles/Profile01/dmgr/bin/backupconfig_03Aug2010_beforeSslChange.zip
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/Profile01/dmgr/logs/restoreConfig.log
ADMU0128I: Starting tool with the dmgr profile
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: dmgr
ADMU2010I: Stopping all server processes for node Server1_Manager
ADMU0512I: Server dmgr cannot be reached. It appears to be stopped.
ADMU5502I: The directory
/opt/IBM/WebSphere/AppServer/profiles/Profile01/dmgr/config already
exists; renaming to
/opt/IBM/WebSphere/AppServer/profiles/Profile01/dmgr/config.old
ADMU5504I: Restore location successfully renamed
ADMU5505I: Restoring file
/opt/IBM/WebSphere/AppServer/profiles/Profile01/dmgr/bin/backupconfig_03Aug2010_beforeSslChange.zip
to location
/opt/IBM/WebSphere/AppServer/profiles/Profile01/dmgr/config
………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………..ADMU5506I: 560 files successfully restored
ADMU6001I: Begin App Preparation –
ADMU6009I: Processing complete.