The backupConfig command is a simple utility to back up the configuration of your node to a file.
This topic 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 WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.
sptcfgBy 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 Using command line tools. 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.
Issue the command from the profile_root/bin directory.
The command syntax is as follows:
backupConfig.sh 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 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
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