Restoring migrated components to previous versions

You can restore or revert migrated components to previous versions of WebSphere Message Broker. For some components, you restore them to the previous version and their original state; for other components, you revert them to the previous version, but keep any changes that you have made to them, such as deployed message flows.

You might want to restore or revert components if you encounter a problem after you have migrated your broker domain to Version 6.0. By restoring or reverting components to the previous level, you can fix the problem with Version 6.0. There is no need to revert the entire domain; revert only those components that are causing a problem. For example, if a message flow does not work as expected in Version 6.0, revert that broker until you can resolve the problem.

You can revert components to a previous version only if they were migrated from that version originally. You cannot create a new Version 6.0 broker, then revert it to a previous level. Nor can you create a Version 2.1 broker, migrate it to Version 6.0, then revert it to Version 5.0.

The topics in this section explain how to restore or revert components and resources that you have migrated from Version 5.0 or Version 2.1 products back to their original state:
Related concepts
Conditions for using migrated resources with previous versions of the Message Brokers Toolkit
Related tasks
Migrating and upgrading
Backing up Version 2.1 resources
Backing up WebSphere Business Integration Message Broker Version 5.0 resources
Uninstalling