To substitute an unrecoverable queue manager with it's backup queue manager, do the following:
strmqm -a BackupQMName
The
backup queue manager is activated. Now active, the backup queue manager can
no longer be updated.strmqm BackupQMName
WebSphere MQ regards this
as restart recovery, and utilizes the log from the backup queue manager. During
the last update to the backup queue manager replay will have occurred, therefore
only the active transactions from the last recorded checkpoint are rolled
back.
When an unrecoverable queue manager is substituted for a backup queue manager some of the queue manager data from the unrecoverable queue manager can be lost. The amount of lost data is dependent on how recently the backup queue manager was last updated. The more recently the last update, the less queue manager data loss.
Check the resulting directory structure to ensure that you have all the required directories.
See Appendix B. Directory structure (Windows systems) and Appendix C. Directory structure (UNIX systems) for more information about WebSphere MQ directories and subdirectories.
Make sure that you have a log control file as well as the log files. Also check that the WebSphere MQ and queue manager configuration files are consistent so that WebSphere MQ can look in the correct places for the restored data.
If the data was backed up and restored correctly, the queue manager will now start.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
basto5 |