WebSphere Message Brokers
File: an20141_
Writer: Bill Oppenheimer

Task topic

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

Backing up the broker domain on distributed systems

These steps tell you how to back up a broker 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. For more information about carrying out these steps, see the links at the end of this topic.
To back up the components:
  1. Stop each broker.
  2. Stop the Configuration Manager.
  3. Back up the Configuration Manager data repository using the mqsibackupconfigmgr command.
  4. Back up each broker database.
    For example, for a DB2 broker database use the Backup wizard in the DB2 Control Center, or a command similar to:
    DB2 BACKUP DATABASE <broker db> TO "<backup directory>"
  5. Back up the system work path.
    The work path 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
    and any broker-specific work paths. These paths are the ones specified by the -w flag on the mqsicreatebroker command.
To restore the components:
  1. Stop and remove the existing components in the Configuration Manager domain.
    1. Disconnect from the domain on the Message Broker Toolkit.
    2. Stop each broker.
    3. Stop the Configuration Manager.
    4. Delete each broker using the mqsideletebroker command, specifying the -w parameter, which is an optional parameter on Windows and UNIX platforms that deletes from the work path all files related to these brokers.
    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.
  2. Recreate the components.
    1. Create the Configuration Manager.
    2. Create each broker.
  3. Restore the components.
    1. Restore any work paths.
    2. If you are restoring a Configuration Manager that was backed up on z/OS, restore the Configuration Manager repository using the mqsirestoreconfigmgr command.

      Replace the previously backed-up service.properties file

    3. Restore each broker database.
      For example, for a DB2 broker database use the Restore wizard in the DB2 Control Center, or a command similar to:
      DB2 RESTORE DATABASE <broker db> FROM "<backup directory>" TAKEN AT <datetime> 
    4. Start the Configuration Manager.
    5. Start each broker.
    6. Connect to the Configuration Manager on the Message Broker Toolkit. This re-imports the broker topology, excluding execution groups and flows, from the Configuration Manager.
    7. Deploy the topology configuration on the Message Broker Toolkit. This causes the Configuration Manager to give the UUIDs to the brokers. Note that if you are working on a platform other than Windows, this step is unnecessary.
Related tasks
Starting and stopping a Configuration Manager
Creating the databases
Connecting components
Deploying a publish/subscribe topology
Starting and stopping a broker on Linux and UNIX systems
Starting and stopping a broker on Windows
Related reference
Supported databases
mqsicreatebroker command
mqsicreateconfigmgr command
mqsistop command
mqsistart command
mqsideletebroker command
mqsideleteconfigmgr command
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:49

an20141_ This topic's URL is: