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.
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:
Usage scenario
The following example demonstrates correct syntax:
backupConfigThis example creates a new file that includes the current date. For example: WebSphereConfig_2003-04-22.zip
backupConfig myBackup.zip -nostopThis example creates a file called myBackup.zip, and does not stop any servers before beginning the backup process.