Restoring a profile

• Use the restoreConfig command to restore a profile configuration using an archive previously generated using backupConfig.
  

• If the configuration to be restored exists, the config directory is renamed to config.old (then config.old_1, etc.) before the restore begins.

• The command then restores the entire contents of the <profile_home>/config directory.

• By default, all servers on the node stop before the configuration restores so that node synchronization does not occur during the restoration.

• Executing restoreConfig from the <was_home>/bin directory without the -profileName parameter will restore the default directory.

• Executing restoreConfig from the <profile_home>/bin directory without the -profileName parameter will restore that profile.

• restoreConfig.bat <backup_file> restores the node configuration to the WAS_HOME/config directory structure

  RestoreConfig <backup_file> [options]

-nowait	Do not wait for the servers to be stopped before backing up the configuration.
-quiet	Suppresses the printing of progress information.
-location <directory_name>	Location of the backup file.
-logfile <fileName>	Location of the log file to which information gets written. The default is <profile_home>/logs/backupConfig.log.
-profileName <profile>	Profile to run the command against. If the command is run from <was_home>/bin and -profileName is not specified, the default profile is used. If run from <profile_home>/bin, that profile is used.
-replacelog	Replaces the log file instead of appending to the current log.
-trace	Generates trace information into the log file for debugging purposes
-username <name>	User name for authentication if security is enabled in the serve
-password <password>	Specifies the password for authentication if security is enabled.

Taking the backup of Configuration

• The backupConfig command is a simple utility to back up the configuration of your node to a file .

• By default, all servers on the node stop before the backup is made so that partially synchronized information is not saved.

• You can run this command from the install_root/bin directory of a WebSphere Application Server installation or a network deployment installation.

• In a UNIX or Linux environment, the backupConfig command does not save file permissions or ownership information.

• The restoreConfig command uses the current umask and effective user ID (EUID) to set the permissions and ownership when restoring a file.

• If it is required that the restored files have the original permissions and ownership, use the tar command (available on all UNIX or Linux systems) to backup and restore the configuration .

     backupConfig <backup_file> [options]

    

Options	Description
- 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 <fileName>	Specifies the location of the log file to which information gets written.
-replacelog	Replaces the log file instead of appending to the current log.
-trace	Generates trace information into the log file for debugging purposes.
-username <name>	Specifies the user name for authentication if security is enabled in the server. Acts the same as the -user option.
-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.

    

 

    Usage scenario:

   

backupConfig

backupConfig myBackup.zip –nostop

Creates a file called myBackup.zip, and does not stop any servers before beginning the backup process

Note: Executing backupConfig from the <was_home>/bin directory without the  -profileName parameter will back up the default directory.

Executing backupConfig from the <profile_home>/bin directory without the -profileName parameter will back up that profile.

To back up a cell configuration, specify the deployment manager profile in the -profileName parameter.

 Examples:

[suvash@hostname ~]$ date;sudo /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/backupConfig.sh;date

Mon Jun 13 12:43:20 CEST 2011

ADMU0116I: Tool information is being logged in file

           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/backupConfig.log

ADMU0128I: Starting tool with the Dmgr01 profile

ADMU5001I: Backing up config directory

           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config to file

           /home/cpandey/WebSphereConfig_2011-06-13.zip

ADMU0505I: Servers found in configuration:

ADMU0506I: Server name: dmgr

ADMU2010I: Stopping all server processes for node dmgacc1Manager

ADMU0512I: Server dmgr cannot be reached. It appears to be stopped.

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

ADMU5002I: 2,251 files successfully backed up

Mon Jun 13 12:45:58 CEST 2011

[suvash@hostname ~]$ date;ls -l /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/*.zip

-rw-r--r--  1 root     root    1234339082 Jun 13 12:45 WebSphereConfig_2011-06-13.zip