Updating a backup queue manager

To ensure that a backup queue manager remains an effective method for disaster recovery it must be updated regularly.

About this task

Regular updating lessens the discrepancy between the backup queue manager log, and the current queue manager log. There is no need to stop the queue manager before you back it up.

Warning: If you copy a non-contiguous set of logs to the backup queue manager log directory, only the logs up to the point where the first missing log is found is replayed.

Procedure

Issue the following Script (MQSC) command on the queue manager to be backed up:
```
RESET QMGR TYPE(ADVANCELOG)
```
This stops any writing to the current log, and then advances the queue manager logging to the next log extent. This ensures you back up all information logged up to the current time.
Obtain the (new) current active log extent number by issuing the following Script (MQSC) command on the queue manager to be backed up:
```
DIS QMSTATUS CURRLOG
```
Copy the updated log extent files from the current queue manager log directory to the backup queue manager log directory.
Copy all the log extents since the last update, and up to (but not including) the current extent noted in 2. Copy only log extent files, the ones beginning with "S...".
Run the strmqm control command on the backup queue manager as shown in the following example:
```
strmqm -r BackupQMName
```
This replays all the copied log extents and brings the backup queue manager into step with the queue manager. When the replay finishes you receive a message that identifies all the log extents required for restart recovery, and all the log extents required for media recovery.