Switching over to a recovery node

If a disaster occurs in your main site, you take steps to switch over to your recovery site.


Following the loss of the primary queue manager at the main site, you make secondary queue manager at the recovery site into the primary and start it. Applications reconnect to the queue manager at the recovery site and the queue manager processes application messages. We can also use this procedure to test your recovery node.

Important: We must ensure that the primary instance of a queue manager is stopped and made into a secondary instance before you promote the original secondary instance. Otherwise partitioned data can accrue.

We must either be logged in as root or logged in as a user who belongs to the mqm group and has the necessary sudo configuration.


Procedure

  1. If we are using this procedure to test your secondary queue manager (that is, the primary instance is still running), we must stop the primary instance and redesignate it as the secondary instance: 
    endmqm qmname
rdqmdr -m qmname -s
  2. Make the secondary queue manager into the primary by entering the following command on the recovery node: 
    rdqmdr -m qmname -p
  3. Start the queue manager by entering the following command: 
    strmqm qmname
  4. Ensure that the applications reconnect to the queue manager on the recovery appliance. Provided that we have defined your channels with a list of alternative connection names, specifying your primary and secondary queue managers, then the applications will automatically connect to the new primary queue manager.

Parent topic: Operate in a disaster recovery environment


Related information