Previous | Next


Migrate nodes

 


Step 12: Scenario 1: Migrate a cell using the command line tools

Start the v8.0 dmgr.

Use the same source node name and cell name for each node that you migrate to v8.0.

For each node you plan to migrate, execute...

  1. Create the target node profile. 
    cd /opt/WASv8/bin
./manageprofiles.sh -create
                    -profileName node1
                    -templatePath /opt/WASv8/profileTemplates/managed
                    -nodeName currentNode1Name
                    -cellName currentCellName
                    -hostName mynode1host.company.com

  2. Save the current node X configuration information to a migration backup directory. Choose a new directory for the backup files. For example: 
    cd /opt/WASv8/bin/
./WASPreUpgrade.sh /mybackup/v61tov8node1 /opt/WASv61  -oldProfile 61node1

  3. If the WASPreUpgrade command completed with Success, then checking the logs for errors or warnings is not necessary.

  4. Check the WASPreUpgrade console output for the following messages: "Failed with errors" or "Completed with warnings".

  5. Look in the following logs for warnings or errors:

    • migration_backupdir/logs/WASPreUpgrade.oldProfile.timestamp.log
    • migration_backupdir/logs/WASPreUpgrade.trace

  6. Stop the node agent on the node being migrated. If you do not stop the node agent, you might encounter corruption problems.

  7. Restore the saved node X configuration into the new v8.0 managed profile. For example: 
    cd /opt/WASv8/bin/
./WASPostUpgrade.sh /mybackup/v61tov8node1
                    -profileName v61tov8node1
                    -oldProfile 61node1
                    -replacePorts TRUE
                    -backupConfig TRUE
                    -scriptCompatibility TRUE
                    -username myuser -password mypass

    The script compatibility flag on your dmgr must be the same as the flag that you use on your nodes.

  8. If the command completed with Success, then checking the logs for errors or warnings is not necessary.

  9. Check the WASPostUpgrade console output for the following messages: "Failed with errors" or "Completed with warnings".

  10. Look in the following logs for errors or warnings:

    • migration_backupdir/logs/WASPostUpgrade.target_profile.timestamp.log
    • migration_backupdir/logs/WASPostUpgrade.target_profile.trace

    If the WASPostUpgrade command fails, you may have to restore the v8.0 dmgr from the backupConfig file. If the WASPostUpgrade processing executed the syncNode command, then the dmgr is aware that the node X has been migrated. The node X cannot be migrated again until the dmgr has been restored to the state before the node X migration.

  11. Check the v8.0 dmgr SystemOut.log for warnings or errors.

  12. Start the migrated v8.0 node X agent.

  13. Check the v8.0 dmgr and node X SystemOut.log for warnings or errors.

  14. Synchronize the cell.

  15. Stop all the application servers on the v8.0 migrated node X.

  16. Start the appropriate application servers on the v8.0 migrated node X.

  17. Save the v8.0 profile configuration to a file... 
    cd /opt/WASv8/profiles/v61tov8node1/bin/
./backupConfig.sh /mybackupdir/v61tov8node1.zip
                  -username myuser
                  -password mypass
                  -nostop

    Each time you run the backupConfig command, use a new backup file name.

  18. Save the dmgr configuration. On the v8 dmgr host... 

    cd /opt/WASv8/profiles/v61v8dmgr01/bin/
./backupConfig.sh /mybackupdir/v61v8dmgr01/backupMigratedDmgrPlusNodeX.zip -username myuser -password mypass

    If you are migrating a node to a different host, refer to these steps in Scenario 2: Migrating cells across operating systems using the command-line tools.

    For each node migrated, backup the v8 Deployment Manager configuration to a new backup file.


Support information (generally applicable)


What to do next

Troubleshoot




+

Search Tips   |   Advanced Search