In the case of a total loss of a WebSphere MQ computing center, you can recover on another queue manager or queue-sharing group at a recovery site. (See Recovering a queue-sharing group at the alternative site for the alternative site recovery procedure for a queue-sharing group.)
To recover on another queue manager at a recovery site, you must regularly back up the page sets and the logs. As with all data recovery operations, the objectives of disaster recovery are to lose as little data, workload processing (updates), and time, as possible.
At the recovery site:
When you have done this, reestablish all your queue managers as described in the following procedure. This can be used to perform disaster recovery at the recovery site for a single queue manager. It assumes that all that is available are:
You can use dual logging for the active and archive logs, in which case you need to apply the BSDS updates to both copies:
The BSDS now describes all active logs as being empty, all the archived logs you have available, and no checkpoints beyond the end of your logs.
CSQJ245D +CSQ1 RESTART CONTROL INDICATES TRUNCATION AT RBA highrba. REPLY Y TO CONTINUE, N TO CANCEL
Type Y to start the queue manager. The queue manager starts, and recovers data up to ENDRBA specified in the CRESTART statement.
See Using the WebSphere MQ Utilities for information about using CSQJU003 and CSQJU004.
Figure 47 shows sample input statements for CSQJU003 for steps 6, 7, and 8:
* Step 6 DELETE DSNAME=MQM2.LOGCOPY1.DS01 DELETE DSNAME=MQM2.LOGCOPY1.DS02 DELETE DSNAME=MQM2.LOGCOPY1.DS03 DELETE DSNAME=MQM2.LOGCOPY1.DS04 DELETE DSNAME=MQM2.LOGCOPY2.DS01 DELETE DSNAME=MQM2.LOGCOPY2.DS02 DELETE DSNAME=MQM2.LOGCOPY2.DS03 DELETE DSNAME=MQM2.LOGCOPY2.DS04 * Step 7 NEWLOG DSNAME=MQM2.LOGCOPY1.DS01,COPY1 NEWLOG DSNAME=MQM2.LOGCOPY1.DS02,COPY1 NEWLOG DSNAME=MQM2.LOGCOPY1.DS03,COPY1 NEWLOG DSNAME=MQM2.LOGCOPY1.DS04,COPY1 NEWLOG DSNAME=MQM2.LOGCOPY2.DS01,COPY2 NEWLOG DSNAME=MQM2.LOGCOPY2.DS02,COPY2 NEWLOG DSNAME=MQM2.LOGCOPY2.DS03,COPY2 NEWLOG DSNAME=MQM2.LOGCOPY2.DS04,COPY2 * Step 8 CRESTART CREATE,ENDRBA=063000
The things you need to consider for restarting the channel initiator at the recovery site are similar to those faced when using ARM to restart the channel initiator on a different z/OS image. See Using ARM in a WebSphere MQ network for more information. Your recovery strategy should also cover recovery of the WebSphere MQ product libraries and the application programming environments that use WebSphere MQ (CICS(R), for example).
Other functions of the change log inventory utility (CSQJU003) can also be used in disaster recovery scenarios. The HIGHRBA function allows the update of the highest RBA written and highest RBA off-loaded values within the bootstrap data set. The CHECKPT function allows the addition of new checkpoint queue records or the deletion of existing checkpoint queue records in the BSDS.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq8495 |