backupConfig command

backupConfig will back up a node configuration to a file.

• All servers on the node stop before the backup is made, so partially synchronized information is not saved.

  If we do not have root authority, specify a path for the backup file in a location where we have write permission. The backup file will be in zip format and a .zip extension is recommended.

• 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 back up and restore the configuration.

• backupConfig retrieves user ID and password information from...
  profile_root/properties/ipc.client.props

Steps

1. From dmgr verify nodes are synced.

2. Back up configuration.
   cd profile_root/bin directory
   ./backupConfig.sh /path/to/backup_file [options]

   /path/to/backup_file specifies the file to which the backup is written. If we do not specify one, a unique name is generated.

   If we do not have root authority, specify a path for the backup file in a location where we have write permission. The backup file will be in zip format and a .zip extension is recommended.

3. Restart appservers.

Options

-nostop	Do not stop the servers before backing up the configuration. If this option is used stop appservers manually before running backupConfig.
-quiet	Suppresses the progress information that the backupConfig command prints in normal mode
-logfile file_name	Location of the log file to which trace information is written By default, the log file is named backupConfig.log and is created in the logs directory.
-profileName profile	Defines the profile of the application server process in a multi-profile installation The -profileName option is not required for running in a single-profile environment. The default for this option is the default profile.
-replacelog	Replace the log file instead of appending to the current log
-trace	Generates trace information into the log file for debugging purposes
-username user_name	User name for authentication if security is enabled in the server; acts the same as the -user option
-user user_name	User name for authentication if security is enabled in the server; acts the same as the -username option
-password password	Password for authentication if security is enabled in the server
-help	Prints a usage statement
-?	Prints a usage statement

The following example creates a new file that includes the current date:

backupConfig.sh WebSphereConfig_2005-04-22.zip

(iSeries) The following example creates a file called myprofileBackup.zip under the /home/mydir directory for the myprofile profile.

backupConfig /home/mydir/myprofileBackup.zip -profileName myprofile

The following example creates a file called myBackup.zip and does not stop any servers before beginning the backup process:

backupConfig.sh myBackup.zip -nostop

restoreConfig command

Migration Toolkit on WASdev.

Video: Running the backupConfig and restoreConfig commands in WAS (V8.5.5)