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 line" tools article in the information center. If you do not have root authority, you must 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.
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.
The backupConfig command does not
save authorities that were granted to the configuration directory structure
of the profile. 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 that were
granted.
Issue the command from the profile_root/bin directory.
The command syntax is as follows:
backupConfig.sh backup_file [options]
backupConfig.bat backup_file [options]
backupConfig.sh backup_file [options]
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.
The QEJBSVR user profile must
have *WX authority to the directory path specified in backup_file.
If no path is specified, the QEJBSVR user profile must have *WX authority
to the current working directory.
The following options are available for the backupConfig command:
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
backupConfig.sh WebSphereConfig_2005-04-22.zip
backupConfig WebSphereConfig_2005-04-22.zip
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
backupConfig.sh myBackup.zip -nostop
backupConfig myBackup.zip -nostop