High availability clustering

 

This section gives information on considerations for migrating high availability (HA) clusters.

To update an HA cluster, plan the order of migration so that a system running WebSphere MQ V5.3 code can never access the files for a queue manager that is already running with V6.0 code. Implementing this rolling migration strategy to minimize total downtime will probably require you to disable failover between some systems in the cluster during the upgrade process.

Because channels are objects in WebSphere MQ V6.0, the channels and clntconn directories must be replicated between nodes for channel definitions. (The client channel table file is unchanged.)

On Windows HA systems, the certificate stores must be migrated to GSKit on all nodes which host a WebSphere MQ V6.0 queue manager.

 

Parent topic:

Additional migration information

mi10580_