Posted: Fri May 29, 2020 3:01 am Post subject: MSCS Cluster deployment options for MQ High Availabilty
Acolyte
Joined: 10 Jan 2020 Posts: 50
Hello MQ cluster forum users,
I have a bank customer who is curently using an old (obsolete) Wintel based MQ infra (MQ ver 5.3 to MQ v8.x) and wants to deploy a new MSCS cluster where all stand alone based queue managers from different domains will be hosted (after being migrated).
This old Wintel MQ infra serves 24 x 7 banking applications and connects with queue managers on other platforms (AIX, z/Os).
The reason for maintaining the old MQ infra up to now, was the lack of MQ skills & expertise.
Customer's main scope for the deployment of MSCS MQ HA cluster is to minimize MQ apps downtime and to have a safe patching window (as part of security audit process), which is not currently feasible.
The solution options considered are either MSCS cluster Active/Passive (A-P) or Active/Active (A-A).
I would like to ask the following:
1. Which is the preferable MSCS cluster option (A-P or A-A) to be deployed in terms of MQ Service, objects & message availablity?
2. Is it recommended to deploy both MSCS cluster nodes as VMs (virtualized) instead of physical?
3. Is it feasible to combine MQCluster (shared cluster queues on multiple queue managers) with MSCS Active/Passive or Active/Active? If yes, which are the pros and cons?
4. Is it recommended to deploy MSCS as "geocluster" splitting cluster nodes in separated sites (PROD & DR) with their owned shared storage given that bank has already a dark fiber interconnection between both sites (4 lines x 128 Gbps) using storage replication (VPLEX)?
P.S.
I have reviewed relevant IBM Knowledge Center articles, but i need more customized responses for this particular case:
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum