Next Step   Next Step

Run the backupConfig command on the deployment manager and all old nodes

Map Step 1 towards the goal: Scenario 2: Migrating cells across operating systems using the command-line tools

About this task

If the process fails, save the current deployment manager and node configuration to a file that you can use later for recovery purposes.

Procedure

  1. Change to the deployment_manager_profile_root/bin directory.
  2. Run the backupConfig command with the appropriate parameters and save the current profile configuration to a file. For example:
    /QIBM/UserData/WebSphere/AppServer/V61/ND/profiles/v61dmgr01/bin/backupConfig /mybackup_old_host/v61dmgr01backupBeforeV7migration.zip -username myuser -password mypass -nostop
    
    where mybackup_old_host is the location where the configuration restore points are stored.
  3. For each node in the configuration, change to the node_profile_root/bin directory.
  4. Run the backupConfig command with the appropriate parameters and save the current profile configuration to a file. For example:
    /QIBM/UserData/WebSphere/AppServer/V61/ND/profiles/v61node01/bin/backupConfig /mybackup_old_host/v61node01rbackupBeforeV7migration.zip -username myuser -password mypass -nostop
    

Supporting information (generally applicable)

What to do next

Install WebSphere Application Server Version 7.0

Next Step   Next Step


Terms and conditions for information centers | Feedback

Last updated: Feb 6, 2014 2:51:05 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=tmig_migrate_remote_commandline_step1
File name: tmig_migrate_remote_commandline_step1.html