Backing up the Configuration Manager domain on z/OS

These steps tell you how to back up a Configuration Manager domain so that it can be restored for migration purposes or in the event of an unrecoverable failure. The backup and restoration of a broker needs to extend to every broker that is deployed to by the Configuration Manager. All the topics that you need to carry out these steps are listed in the 'Related information' section at the end of this topic.
To back up the components:
  1. Stop each broker.
  2. Note the BrokerUUID value from the following file: <broker directory>/registry/<broker name>/BrokerUUID.
  3. Stop the Configuration Manager.
  4. Back up the Configuration Manager data repository.
  5. Back up each broker database.

To restore the components:

  1. Stop and remove the existing components in the Configuration Manager domain.
    1. Stop each broker.
    2. Stop the Configuration Manager.
    3. Exit from the Message Brokers Toolkit.
    4. Submit the broker reset job BIPJRSTC in the broker PDSE for each broker (as described in Resetting a broker on z/OS).
    5. Delete the Configuration Manager using the mqsideleteconfigmgr command, specifying the -w and -n parameters. The -n parameter deletes all data in the configuration repository.
    6. Drop the Configuration Manager repository.
  2. Recreate the components.
    1. Create the Configuration Manager repository.
    2. Create the Configuration Manager.
    3. Start the Configuration Manager.
    4. Start each broker.
    5. Run the Message Brokers Toolkit.
    6. Connect to the Configuration Manager.
    7. Add to the Configuration Manager domain new brokers with the same names as the originals.
    8. Deploy the topology configuration.
  3. Restore the components.
    1. Stop each broker.
    2. Stop the Configuration Manager.
    3. Restore the Configuration Manager repository.
    4. Restore each broker database.
    5. Set the BrokerUUID by editing the following file: <broker directory>/registry/<broker name>/BrokerUUID.
    6. Start the Configuration Manager.
    7. Start each broker.
    8. Connect to the Configuration Manager.
    9. Deploy the topology configuration.
Related tasks
Starting and stopping the Configuration Manager
Creating the databases
Connecting components
Deploying a topology configuration
Starting and stopping a broker on z/OS
Related reference
Supported databases
mqsicreatebroker command
mqsicreateconfigmgr command
mqsistop command
mqsistart command
mqsideletebroker command
mqsideleteconfigmgr command