Backing up the broker domain on z/OS

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:

  1. Stop each broker.
  2. Note the BrokerUUID value from the following file: <broker directory>/registry/<broker name>/CurrentVersion/BrokerUUID.
  3. Stop the Configuration Manager.
  4. Back up the Configuration Manager data repository using the mqsibackupconfigmgr command, or JCL job BIPBUCM.
  5. Back up each broker database using the JCL job BIPBUDB.

Restoring components

  1. Stop and remove the existing components in the Configuration Manager domain.
    1. Disconnect from the domain in the Message Brokers Toolkit.
    2. Stop each broker.
    3. Stop the Configuration Manager.
    4. Delete each broker.
    5. Delete the Configuration Manager.
  2. Recreate the components.
    1. Create the Configuration Manager repository.
    2. Create each broker.
  3. Restore the components.
    1. Restore the Configuration Manager repository using the mqsirestoreconfigmgr command, or JCL job BIPRSCM.
    2. Restore each broker database using the JCL job BIPRSDB.
    3. Set the BrokerUUID by editing the following file: <broker directory>/registry/<broker name>/CurrentVersion/BrokerUUID.
    4. Start the Configuration Manager.
    5. Start each broker.
    6. 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.
    7. Deploy the topology configuration in the Message Brokers Toolkit. This causes the Configuration Manager to give the UUIDs to the brokers.