makedrprimary

Purpose

You use the makedrprimary command on an appliance to identify it as the primary version in a disaster recovery configuration.

You should always check the disaster recovery status of a queue manager before you issue the makedrprimary command on that queue manager. See status.

If you run makedrprimary when the queue manager is in the partitioned state (that is, each appliance has a different version of the queue manager data) the version of the queue manager and associated data on this appliance are identified as the definitive version.

If you run makedrprimary on the recovery appliance when the secondary queue manager is inconsistent (that is, replication has not completed successfully and the queue manager would be unable to start), then the command starts the process of reverting the queue manager to the data snapshot taken before the queue manager became inconsistent. You can monitor the progress of the reversion by using the status command, see status. If the reversion is interrupted for any reason, it will resume and complete. After it has reverted to the snapshot, the queue manager becomes the primary version in the disaster recovery configuration.

If you run makedrprimary on a secondary queue manager after initial synchronization has failed, a message informs you that you cannot do this until the initial synchronization has completed. If the main appliance has failed and will not be restored (so that the initial synchronization can never complete), then the queue manager must be deleted on the recovery appliance by running the dltdrsecondary command.

Parameters

-m QMName

Specifies the queue manager that you are identifying as the primary queue manager in a disaster recovery configuration.