Back up the deployment manager and all old nodes
Parent
Migrate cells using the command-line tools
In case of failure during the migration, save the current deployment manager and node configuration to a file that we can use later for recovery purposes.
- Change to the deployment_manager_profile_root/bin directory.
- Run the backupConfig command with the appropriate parameters and save the current profile configuration to a file. For example:
(dist)
/opt/WebSphereV70/profiles/v70dmgr01/bin/backupConfig.sh /mybackupdir/v70dmgr01backupBeforeV85migration.zip -username myuser -password mypass -nostop
(iseries)/QIBM/UserData/WebSphere/AppServer/V70/ND/profiles/v70dmgr01/bin/backupConfig /mybackupdir/ v70dmgr01backupBeforeV85migration.zip -username myuser -password mypass -nostop
- For each node in the configuration, change to the node_profile_root/bin directory.
- Run the backupConfig command with the appropriate parameters, and save the current profile configuration to a file. For example:
(dist)/opt/WebSphereV70/profiles/v70node01/bin/backupConfig.sh /mybackupdir/ v70node01backupBeforeV85migration.zip -username myuser -password mypass -nostop
(iseries)
/QIBM/UserData/WebSphere/AppServer/V70/ND/profiles/v70node01/bin/backupConfig /mybackupdir/v70node01rbackupBeforeV85migration.zip -username myuser -password mypass -nostop
What to do next
Install WebSphere Application Server v8.5
Subtopics
- backupConfig command
The backupConfig command is a simple utility to back up the configuration of the node to a file.
- restoreConfig command
Use the restoreConfig command to restore the configuration of the node after backing up the configuration using the backupConfig command.
- Directory conventions
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. Become familiar with the conventions in use for WebSphere Application Server.
Related information:
backupConfig command restoreConfig command Directory conventions