Backing up the broker domain on z/OS®

You can back up a broker domain so that it can be restored for migration purposes or in the event of an unrecoverable failure. Back up broker domain resources, and plan for restoration, on every system on which you have installed and created 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. Record 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:
    • Windows platform On Windows® the default directory is:
      C:\Documents and Settings\All Users\Application Data\IBM\MQSI
      The actual value might be different on your computer.
    • Linux platformUNIX platform On other distributed platforms the directory is:
      /var/mqsi

    Keep your saved copy of this file 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 by using the JCL job BIPBUDB.
    Start of changeThe BIPBUDB job contains the following variables:
    Variable Description
    ++BACKUPHLQ++ The high level qualifier of the template for the data set name.
    ++TEMPLATENAME++ The name of the data set allocation template.
    For more information, see the DB2 UDB for z/OS Utility Guide and Reference, SC18-7427. End of change

Restoring components

To restore the 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.
      Start of changeThe BIPRSDB job contains the following variable:
      Variable Description
      ++TOLOGPOINTVALUE++ This variable specifies a point on the log to which RECOVER is to recover. Specify either an RBA or an LRSN value.
      For more information, see the DB2 UDB for z/OS Utility Guide and Reference, SC18-7427. End of change
    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 action 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 deployment causes the Configuration Manager to give the UUIDs to the brokers.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:40:48

an20142_