Home

 

Backing up queue manager data

 

To take a backup copy of a queue manager’s data:

1. Ensure that the queue manager is not running. If you try to take a backup of a running queue manager, the backup might not be consistent because of updates in progress when the files were copied.

   If possible, stop your queue manager in an orderly way. Try executing endmqm -w (a wait shutdown); only if that fails, use endmqm -i (an immediate shutdown).

2. Find the directories under which the queue manager places its data and its log files, using the information in the configuration files. For more information about this, see Configuring WebSphere MQ.

   You might have some difficulty in understanding the names that appear in the directory. The names are transformed to ensure that they are compatible with the platform on which you are using WebSphere MQ. For more information about name transformations, see Understanding WebSphere MQ file names.

3. Take copies of all the queue manager’s data and log file directories, including all subdirectories.

   Make sure that you do not miss any files, especially the log control file and the configuration files (or equivalent Registry entries on Windows). Some of the directories might be empty, but we need them all to restore the backup at a later date, so save them too.

4. Preserve the ownerships of the files. For WebSphere MQ for UNIX systems, we can do this with the tar command. (If you have queues larger than 2 GB, we cannot use tar; for more information, see Enabling large queues.)

 

Parent topic:

Backing up and restoring WebSphere MQ

fa14700_

 

Home