Rolling back environments
After you migrate to a WebSphere® Application Server Version 9.0 environment, you can roll back to your previous environment. This returns the configuration to the state that it was in before migration. After rolling back the environment, you can restart the migration process.
About this task

This article is about profile configuration migration. To migrate your applications to the latest version, use the WebSphere Application Server Migration Toolkit. For more information, see the Migration Toolkit on WASdev.
sptcfgGenerally, migration does not modify anything in the configuration of the
prior release; however, there are cases where minimal changes are made that are reversible. When
using clone migration, a roll back plan is not necessary. The previous environment remains
unchanged. In a Network Deployment Cell, the old nodes are never synchronized to or managed by the
new deployment manager. To reset a clone migration, delete all the nodes in the target cell and
start over.
Procedure
- To roll back a Version 9.0 deployment manager and its federated nodes to Version 7.0 or later, follow the instructions in Rolling back a WebSphere Application Server, Network Deployment cell.
- To roll back a Version 9.0 federated node to Version 7.0 or later, follow the instructions in Rolling back a federated node.
- To roll back a Version 9.0 stand-alone application server to Version 7.0 or later, follow the instructions in Rolling back stand-alone application servers.