WebSphere Message Brokers
File: an20142_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:33:50

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. If you plan to restore the Configuration Manager data repository on distributed systems, take a copy of the file:
    <data directory>/components/<Configuration Manager name>/<directory name>/service.properties
    The <data directory> is platform specific:
    • On Windows the directory is:
      C:\Documents and Settings\All Users\Application Data\IBM\MQSI
    • On the other distributed platforms the directory is:
      /var/mqsi

    This needs to be kept with the .zip file produced by the mqsibackupconfigmgr command, and must be copied to the equivalent place in the restored Configuration Manager data repository after running the mqsirestoreconfigmgr command.

  5. Back up the Configuration Manager data repository using the mqsibackupconfigmgr command, or JCL job BIPBUCM.
  6. 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 Broker 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 Broker Toolkit. This re-imports the broker topology, excluding execution groups and flows, from the Configuration Manager.
    7. Deploy the topology configuration in the Message Broker Toolkit. This causes the Configuration Manager to give the UUIDs to the brokers.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:33:50

an20142_ This topic's URL is: