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. For more information about where to run this command, see the Using command tools article. If you do not have root authority, specify a path for the backup file in a location where you have write permission. The backup file will be in zip format and a .zip extension is recommended.
The backupConfig command does not save authorities which may have been granted to the profile's config directory structure. The restoreConfig command sets the owner of the directory structure and its contents to QEJBSVR and restores private authorities to the QTMHHTTP and QNOTES user profiles (if they exist). It does not restore any other private authorities which may have been granted.
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.
Note: The QEJBSVR user profile must have *WX authority to the directory path specified in backup_file. If no path is specified, QEJBSVR must have *WX authority to the current working directory.
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 /home/mydir/myprofileBackup.zip -profileName myprofile
This example creates file myprofileBackup.zip under directory /home/mydir for profile myprofile.
backupConfig myBackup.zip -nostopThis example creates a file called myBackup.zip, and does not stop any servers before beginning the backup process.