Backing Up MQ Configs

Backing up IBM MQ configuration means preserving the blueprint of your queue manager—every queue name, channel CONNAME, listener port, and security rule—so you can rebuild after hardware failure, corruption, mistaken DELETE, or datacenter loss. Messages on queues are data; object definitions are infrastructure. DR plans that only snapshot disks without readable MQSC exports leave teams guessing attribute values at 3 a.m. Mature estates store desired state in Git, run scheduled exports to detect drift, and backup keystores and ini files with the same discipline as database schema backups. This tutorial explains what to include in config backups, tools such as dmpmqcfg and scripted DISPLAY, file-level backup scope, z/OS catalog and CSQ considerations, pairing config backup with message and log backup, restore testing, retention, and compliance evidence for auditors who ask how quickly you can recreate QM_PROD definitions elsewhere.

Configuration Versus Message Data

Configuration is the repository of objects and queue manager properties. Message data is payload bytes on QLOCAL and transmission queues plus log records. EXPORT and dmpmqcfg capture configuration; media backup and replication capture messages and logs. Restoring config onto a fresh queue manager creates empty queues unless you also restore queue data files from coordinated backup. Document RPO and RTO separately for each.

dmpmqcfg and Platform Utilities

IBM provides dmpmqcfg on supported distributed releases to dump configuration in a structured form suitable for restore with crtmqcfg or equivalent per documentation—verify command names for your version. Schedule dmpmqcfg after change windows into dated directories. Compare yesterday versus today to find drift when someone altered production manually in Explorer. z/OS may use different export paths—consult IBM MQ for z/OS operations guides and CSQUTIL DISPLAY exports.

1
2
3
4
5
# Illustrative distributed backup (verify flags for your MQ version)
dmpmqcfg -m QM1 -o /backup/mq/QM1/config-$(date +%Y%m%d).out
tar -cf /backup/mq/QM1/ini-$(date +%Y%m%d).tar qm.ini mq.ini
# Store OAM separately
dspmqaut -m QM1 > /backup/mq/QM1/auth-$(date +%Y%m%d).txt

Git as Source of Truth

Teams practicing GitOps store MQSC scripts and Terraform IBM MQ resources in version control. The backup is the Git history plus tagged releases. Production must match main branch or documented drift is incident. Pull requests review DEFINE changes like application code. Pair with automated runmqsc deploy to test environments before prod. Git does not replace keystores in vault—never commit private keys.

Explainer: Photocopy of the Building Blueprint

Config backup is photocopying the architect’s blueprint of mailboxes and roads, not photocopying the letters inside the boxes.

File-Level and VM Snapshots

Snapshotting the queue manager directory while running requires crash-consistent or application-consistent backup products that integrate with IBM MQ quiesce guidance. Uncoordinated copy may corrupt repository if taken mid-write. Many sites prefer logical export (dmpmqcfg) over raw file copy for config-only recovery. Message recovery needs log and queue file backup per IBM restore procedures—often with queue manager quiesced or using storage replication.

Security and Keystore Backup

SSLKEYR and AMS keystores must be backed up encrypted with access controls. Restore DR site fails channels if certificates expired or wrong label. Document certificate expiry in the same calendar as config backup tests. RACF profiles on z/OS are backed up with standard RACF utilities—MQ cannot start applications if profiles are missing after LPAR restore.

Restore Testing

1. Quarterly restore QM_RESTORE from latest export on isolated VM.
2. Verify channel ping and application smoke put/get.
3. Measure time to operational from empty VM.
4. Update runbook with actual minutes, not estimates.
5. Fix broken scripts discovered during test.

Retention and Compliance

Retain config backups per regulatory retention—often years for finance. Label with queue manager name, date, and change ticket. Auditors request proof that production ALTER on channel X is traceable to Git commit or backup delta. Immutable storage (WORM, object lock) prevents ransomware from deleting backup catalog.

Hybrid and Multi-Queue-Manager Estates

Backup each queue manager independently—QM_London and QM_NewYork have separate exports. Document channel pairs so restore order recreates both sides. Cloud managed MQ may use cloud provider export APIs plus local Git for client channel definitions and CCDT.

Troubleshooting Backup Gaps

• Export missing new object type — upgrade export tooling for new MQ version features.
• Restore fails attribute validation — MQ version mismatch between export and target.
• Apps 2035 after restore — OAM/RACF not restored or wrong service accounts.
• Channels fail TLS — keystore not restored or wrong password.

Explain Like I'm Five: Backing Up MQ Configs

We save the list of all mailbox names and rules so we can rebuild the post office if the building floods, even if the letters inside are saved separately.

Practice Exercises

Exercise 1

Run export for lab QM; store in dated folder; document restore command from IBM doc.

Exercise 2

List items in your backup that are NOT in Git today.

Exercise 3

Write DR test success criteria for config-only restore.

Frequently Asked Questions

Test Your Knowledge