Rolling back environments
After migrating to a WebSphere Application Server v9.0 environment, we can roll back to the previous environment. This returns the configuration to the state that it was in before migration. After rolling back the environment, we can restart the migration process.
Generally, 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.
Tasks
- To roll back a v9.0 deployment manager and its federated nodes to v7.0 or later, follow the instructions in Rolling back a WAS ND cell.
- To roll back a v9.0 federated node to v7.0 or later, follow the instructions in Rolling back a federated node.
- To roll back a v9.0 stand-alone application server to v7.0 or later, follow the instructions in Rolling back stand-alone application servers.
The configuration should be returned to the state that it was in before migration.
What to do next
Restart the migration process if needed.
Subtopics
- Rolling back a WAS ND cell
- Rolling back a federated node
- Rolling back stand-alone application servers
- Migration Toolkit on WASdev.