Rolling back a managed node

 

You can use the restoreConfig and wsadmin commands to roll back a migrated WAS V6.1 managed node to the state that it was in before migration. For each managed node to roll back, roll back the managed node itself and the corresponding changes made to the master repository located on the deployment manager. Best practice: When migrating a Version 5.x or 6.0.x managed node, the best practice is to perform the following actions if you want to be able to roll it back to its previous state after migration:

1. Back up your existing configuration using the backupConfig command or your own preferred backup utility.

   • Run the backupConfig command or your own preferred utility to back up the V6.1 deployment manager configuration.

     Verify you note the exact name and location of this backed-up configuration.

     See backupConfig command.

   • Run the backupConfig command or your own preferred utility to back up the V5.x or 6.0.x managed node configuration.

     Verify you note the exact name and location of this backed-up configuration.

     See backupConfig command.

2. Migrate the managed node.

If necessary, you can now roll back the managed node that you just migrated.

If you do not have a backup copy of your V6.1 deployment manager configuration as it was before you migrated the V5.x or 6.0.x managed node to roll back, you cannot use the procedure described in this article and roll back your whole cell as described in Rolling back a deployment cell.

 

Overview

You must perform all of the backup and rollback actions for each migrated managed node before you proceed to migrate another managed node.

 

Procedure

1. Stop all of the servers that are currently running in the Version 6.1 environment.

2. Restore your previous configuration.

   1. Run the restoreConfig command or your own preferred utility to restore the V6.1 deployment manager configuration.

      Verify you restore the same backed-up configuration that you created just before you migrated the managed node.

      See restoreConfig command.

   2. Perform one of the following actions to restore the Version 5.x or 6.0.x configuration for the managed node.

      • Run the restoreConfig command or your own preferred utility to restore the V5.x or 6.0.x configuration.

        Make sure that you restore the same backed-up configuration that you created just before you migrated this managed node.

        See restoreConfig command.

      • Use the wsadmin command to run the migrationDisablementReversal.jacl script from the V5.x or 6.0.x profile_root/bin directory of the managed node. In a Linux environment, for example, use the following parameters:

        ./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
        

        If you have trouble running the migrationDisablementReversal.jacl script, try to manually perform the steps in the script.

        1. Go to the following directory:

           profile_root/config/cells/cell_name/nodes/node_name
           

           where node_name is the name of the managed node to roll back.

        2. If you see a serverindex.xml_disabled file in in this directory, perform the following actions:

           1. Delete or rename the serverindex.xml file.

           2. Rename the serverindex.xml_disabled file to serverindex.xml.

3. Start the V6.1 deployment manager.

4. Synchronize the managed node.

   See Synchronizing nodes with the wsadmin tool.

5. If you chose to keep the installed applications in the same location as the prior release during migration to V6.1 and any of the Version 6.1 applications are not compatible with the prior release, install applications that are compatible.

6. Delete the V6.1 managed profile.

   See Deleting a profile.

7. Start the rolled-back managed node in the V6.1 environment.

 

Results

The configuration should now be returned to the state that it was in before migration.

 

What to do next

You can now restart the migration process if you want to do so.