Backing up the Configuration Manager domain on distributed systems

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 in the following way:
    • On Windows, use regedit to examine HKLM\SOFTWARE\IBM\WebSphereMQIntegrator\<BROKER_NAME>\BrokerUUID and note the BrokerUUID value.
    • On UNIX, use cat $MQSI_REGISTRY/registry/VBROKER_NAME>/BrokerUUID and note the BrokerUUID value.
  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. 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 workpath 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.
    6. Drop each broker database.
    7. Drop the Configuration Manager repository.
  2. Recreate the components.
    1. Create each broker database.
    2. Create the Configuration Manager repository.
    3. Create the Configuration Manager.
    4. Create each broker.
    5. Start the Configuration Manager.
    6. Start each broker.
    7. Run the Message Brokers Toolkit.
    8. Connect to the Configuration Manager.
    9. Add to the Configuration Manager domain new brokers with the same names as the originals.
    10. 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 to the value that you noted during backup in the following way:
      • On Windows, use regedit to set HKLM\SOFTWARE\IBM\WebSphereMQIntegrator\<BROKER_NAME>\BrokerUUID to the value that you noted during backup.
      • On UNIX, use print -n <VALUE_NOTED> <$MQSI_REGISTRY/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 UNIX platforms
Starting and stopping a broker on Windows
Related reference
Supported databases
mqsicreatebroker command
mqsicreateconfigmgr command
mqsistop command
mqsistart command
mqsideletebroker command
mqsideleteconfigmgr command