The following instructions describe how to
back up a broker domain so that it can be restored for migration purposes,
or in the event of an unrecoverable failure. You should back
up, and plan for restoration, on every system on which there is a broker or
other broker domain component. For more information about carrying out these
steps, see the links at the end of this topic.
Backing up components
To back up the components:
Stop each broker.
Note the BrokerUUID value from the following file: <broker
directory>/registry/<broker name>/CurrentVersion/BrokerUUID.
Stop the Configuration
Manager.
Back up the Configuration
Manager data repository
using the mqsibackupconfigmgr command,
or JCL job BIPBUCM.
Back up each broker database using the JCL job BIPBUDB.
Restoring components
Stop and remove the existing components in the Configuration
Manager domain.
Disconnect from the domain in the Message Brokers Toolkit.
Stop each broker.
Stop the Configuration
Manager.
Delete each broker.
Delete the Configuration
Manager.
Recreate the components.
Create the Configuration
Manager repository.
Create each broker.
Restore the components.
Restore the Configuration
Manager repository
using the mqsirestoreconfigmgrcommand,
or JCL job BIPRSCM.
Restore each broker database using the JCL job BIPRSDB.
Set the BrokerUUID by editing the following file: <broker
directory>/registry/<broker name>/CurrentVersion/BrokerUUID.
Start the Configuration
Manager.
Start each broker.
Connect to the Configuration
Manager in the Message Brokers Toolkit. This re-imports the
broker topology, excluding execution groups and flows, from the Configuration
Manager.
Deploy the topology configuration in the Message Brokers Toolkit. This causes the Configuration
Manager to give the
UUIDs to the brokers.