IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Backing up the broker

Back up the broker configuration and all associated resources.

Before you start: Create the broker.

You can back up the broker and its resources to preserve the current state of the broker configuration. You can use the backup file that is created to restore a broker in an identical operating environment: the operating system must be at the same level, and the broker and queue manager names must be identical.

You can run this command for a broker that is active. However, you must not take a backup while the broker is processing configuration changes and deployments; the backup file created might contain incomplete information. If the file contains partial records, you cannot use it to restore the broker at a later time.

To ensure that the backup is complete and correct, take a backup either when the broker is not processing a configuration change (such as a deployment or change property) or when the broker is stopped.

  1. If you want to back up an active broker, check that no configuration change requests are in progress. For example, if you are changing broker properties, or have initiated a deployment, wait for these actions to complete before you back up the broker. Active message flows are unaffected by the backup process.

    If you prefer, you can stop the broker before you take a backup by using the mqsistop command.

  2. Back up the broker. Specify the broker name and the location in which the backup file is created. You can also optionally specify the name of the backup file, and the name of a file to which a detailed trace is written.
    • Linux platformUNIX platformWindows platformRun the mqsibackupbroker command, specifying the broker name and the directory to which the backup file is written.

      For example, to back up a broker on Windows, enter the following command:

      mqsibackupbroker IB9NODE -d c:\MQSI\BACKUP
    • z/OS platformCustomize and submit the JCL member BIPBUBK.
  3. When the command has completed successfully, you can continue to use the broker. If you stopped the broker, restart it by using the mqsistart command.
The current broker configuration is saved in the backup file. Keep the file safe so that you can restore the broker at a later date if required.

bn43020_.htm | Last updated Friday, 21 July 2017