4.9.2 Restoring a profile
Use the restoreConfig command to restore a profile configuration using an archive previously generated using backupConfig. If the configuration to be restored exists, the config directory is renamed to config.old (then config.old_1, etc.) before the restore begins. The command then restores the entire contents of the <profile_home>/config directory. By default, all servers on the node stop before the configuration restores so that a node synchronization does not occur during the restoration.
| -
| Executing restoreConfig from the <was_home>/bin directory without the -profileName parameter will restore the default directory.
|
| -
| Executing restoreConfig from the <profile_home>/bin directory without the -profileName parameter will restore that profile.
|
Syntax:
restoreConfig <backup_file> [options]
where backup_file specifies the file to be restored. If you do not specify one, the command will not run.
The parameters are shown in Table 4-18.
Table 4-18
| Parameter
| Description
|
| -nowait
| Do not wait for the servers to be stopped before backing up the configuration.
|
| -quiet
| Suppresses the printing of progress information.
|
| -location <directory_name>
| Location of the backup file.
|
| -logfile <fileName>
| Location of the log file to which information gets written. The default is <profile_home>/logs/backupConfig.log.
|
| -profileName <profile>
| Profile to run the command against. If the command is run from <was_home>/bin and -profileName is not specified, the default profile is used. If run from <profile_home>/bin, that profile is used.
|
| -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>
| User name for authentication if security is enabled in the server.
|
| -password <password>
| Specifies the password for authentication if security is enabled.
|
| -help or -?
| Prints command syntax information.
|
restoreConfig parameters
| 
