Migrating replicated data queue managers
When we need to migrate replicated data queue managers (RDQMs), we must upgrade all nodes in a sequence. Do not try to operate with the nodes at different levels. This guidance is appropriate for moving between major releases, or CD releases, but not for applying (fix pack) maintenance.
About this task
The upgrade sequence for HA RDQM configurations consists of suspending a node, uninstalling IBM MQ and RDQM support, installing the newer version of IBM MQ and RDQM support, then resuming the node. You then move on and repeat this sequence on the next node. Following this sequence ensures that your queue managers continue to run on one of the nodes in the HA group while the migration is in progress.
The upgrade sequence for DR RDQM configurations consists of upgrading the recovery node, running the DR queue managers on the newly upgraded recovery node, upgrading the primary node, switching the DR queue managers back to running on the primary node.
The upgrade sequence for DR/HA RDQM configurations consists of upgrading the HA group on the recovery site, performing a managed failover from the main site to the recovery site, and then upgrading the HA group on the main site before failing the queue managers back to the main site.
We can back up a replicated data queue manager before migration.- Migrating HA RDQMs
Follow this sequence of steps to upgrade all the RDQM nodes in an HA group and so migrate the replicated data queue managers (RDQMs). - Migrating DR RDQMs
Follow this sequence of steps to upgrade the primary and recovery nodes in a disaster recover replicated data queue manager (DR RDQM) configuration. - Migrating DR/HA RDQMs
Follow these steps to upgrade all the RDQM nodes in both HA groups in a DR/HA configuration, and so migrate the replicated data queue managers (RDQMs).
Parent topic: Migrating IBM MQ
Related information