backupConfig command

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 $WAS_HOME/bin directory of a WebSphere Application Server installation or a network deployment installation.

 

Syntax

The command syntax is as follows

backupConfig <backup_file> [options]
where backup_file specifies the file to which the backup is written. If you do not specify one, a unique name is generated.

 

Parameters

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 <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.

-? Prints a usage statement.

 

Usage scenario

The following example demonstrates correct syntax

backupConfig
This example creates a new file that includes the current date. For example: WebSphereConfig_2003-04-22.zip

backupConfig myBackup.zip -nostop
This example creates a file called myBackup.zip, and does not stop any servers before beginning the backup process.