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. 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. Stop the Configuration Manager.
  3. Back up the Configuration Manager data repository using the mqsibackupconfigmgr command.
  4. Start of changeIf you plan to restore the Configuration Manager data repository on distributed systems, you must 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.

    End of change
  5. 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>"
  6. 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 Brokers 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. 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 Brokers Toolkit. This re-imports the broker topology, excluding execution groups and flows, from the Configuration Manager.
    7. Deploy the topology configuration on the Message Brokers 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