Use the mqsibackupbroker command to back up the current configuration of an integration node.
The mqsibackupbroker command creates a record of the current configuration of an integration node in a file, in compressed file format. You can use the file to restore the integration node at a later time, if required.
The command backs up of the following persistent configuration data associated with the integration node:
The command does not back up the following resources:
Use the backup file to restore an integration node on a computer that has an identical configuration; the operating system must be at the same level, and the integration node and queue manager names must be identical.
You can run this command for an integration node that is active. However, you must not take a backup while the integration node 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 integration node at a later time.
To ensure that the backup is complete and correct, either take a backup when the integration node is not processing a configuration change (such as a deployment or change property) or when the integration node is stopped.
The command creates a backup file that contains all available information; if it cannot access some configuration detail, that subset of data is not saved. For example, if a message flow required exclusive access to a deployed resource, and the message flow is running, the deployed resource might not be included in the backup file.
If you do not specify this option, the command fails if it cannot create complete backup file.
Specify this option only if directed to do so by your IBM® service representative.
The following example backs up integration node IBNODE on Windows:
mqsibackupbroker IBNODE -d C:\MQSI\BACKUP -v C:\MQSI\BACKUP\trace.log