Backing up and restoring IBM® MQ queue manager data
Backing up queue managers and queue manager data.
Periodically, you can take measures to protect queue managers against possible corruption caused by hardware failures. There are three ways of protecting a queue manager:
- Back up the queue manager data
- If the hardware fails, a queue manager might be forced to stop. If any queue manager log data is lost due to the hardware failure, the queue manager might be unable to restart. If you back up queue manager data you might be able to recover some, or all, of the lost queue manager data.
In general, the more frequently you back up queue manager data, the less data you lose in the event of hardware failure that results in loss of integrity of the recovery log.
To back up queue manager data, the queue manager must not be running.
To back up and restore queue manager data see: - Use a backup queue manager
- If the hardware failure is severe, a queue manager might be unrecoverable. In this situation, if the unrecoverable queue manager has a dedicated backup queue manager, the backup queue manager can be activated in place of the unrecoverable queue manager. If it was updated regularly, the backup queue manager log can contain log data that includes the last complete log from the unrecoverable queue manager.
A backup queue manager can be updated while the existing queue manager is still running.
To create and activate a backup queue manager see:
- Back up the queue manager configuration only
- If the hardware fails, a queue manager might be forced to stop. If both the queue manager configuration and log data is lost due to the hardware failure, the queue manager will be unable to restart or to be recovered from the log. If you back up the queue manager configuration you would be able to recreate the queue manager and all of its objects from saved definitions.
To back up queue manager configuration, the queue manager must be running.
To back up and restore the queue manager configuration see: