backupConfig command

backupConfig command

The backupConfig command is a simple utility to back up the configuration of the node to a file.
Supported configurations:
This article is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WAS to the latest product version. sptcfg
By default, all servers on the node stop before the backup is made so that 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.
To avoid user ID and password prompts, add the user ID and password information to...
profile_root/properties/ipc.client.props

Issue the command from the profile_root/bin directory.
Command syntax...

backupConfig.sh backup_file [options]

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

Parameters

The following options are available for the backupConfig command:

-nostop Do not stop the servers before backing up the configuration
-quiet Suppress 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_name Define 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 Generate 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 Print a usage statement
-? Print a usage statement

Usage

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

backupConfig.sh WebSphereConfig_2005-04-22.zip

backupConfig.bat WebSphereConfig_2005-04-22.zip
(zos)
backupConfig.sh WebSphereConfig_2005-04-22.zip
(iseries)
backupConfig 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

backupConfig.bat myBackup.zip -nostop
(zos)
backupConfig.sh myBackup.zip -nostop
(iseries)
backupConfig myBackup.zip -nostop

Related information:

restoreConfig command

-nostop	Do not stop the servers before backing up the configuration
-quiet	Suppress 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_name	Define 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	Generate 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	Print a usage statement
-?	Print a usage statement