Multi-instance queue managers improve availability by automatically switching to a
standby server if the active server fails. The active and standby servers are multiple instances of
the same queue manager; they share the same queue manager data. If the active instance fails you
need to transfer its journal to the standby that takes over so that the queue manager can rebuild
its queues.
Configure the IBM® i systems you are running
multi-instance queue managers on so that, if the active queue manager instance fails, the journal it
is using is available to the standby instance that takes over. We can design your own configuration
and administration tasks to make the journal from the active instance available to the instance that
takes over. If we do not want to lose messages, your design must ensure the standby journal is
consistent with the active journal at the point of failure. We can adapt your design from one of
the two configurations that are described with examples in subsequent topics that do maintain
consistency.
Mirror the journal from the system that is running the active queue manager instance to the
systems that are running standby instances.
Place the journal in an Independent Auxiliary Storage Pool (IASP) that is transferable from the
system running the active instance to a standby instance.
The first solution requires no additional hardware or software as it uses basic ASPs. The second
solution requires switchable IASPs which need IBM i
clustering support that is available as a separately priced IBM i License Product 5761-SS1 Option 41.