ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » Moving MQ Cluster Full Repository to new queue manager on ne

Post new topic  Reply to topic
 Moving MQ Cluster Full Repository to new queue manager on ne « View previous topic :: View next topic » 
Author Message
mbwagner
PostPosted: Thu Nov 10, 2016 1:54 pm    Post subject: Moving MQ Cluster Full Repository to new queue manager on ne Reply with quote

Novice

Joined: 24 Feb 2016
Posts: 17

Hi All,

I would like to know your inputs on how to move existing MQ full repository queue manager into new hardware queue manager (New MQ Full Repository Queue Manager name is different).

Present MQ cluster Full Repositories queue manager name is CPQM1 and CPQM2 on WebSphere MQ Version 7.0 on AIX Operating System
Present MQ cluster - There are 8 MQ partial repositories queue manager to interconnect with CPQM1 and CPQM2 (4 PR QM interconnect to CPQM1 and other 4 PR QM interconnect with CPQM2)
New WebSphere MQ Full Repositories Queue Manager name CPQMFR001 and CPQMFR002 on WebSphere MQ 7.5.02 on AIX Operating System

Note - New WebSphere MQ Infrastructure Full Repositories queue manager names are different than existing MQ full repositories.

As MQ Infocenter best practices, we have to perform below task activities to add new MQ full repositories queue manager in the existing MQ cluster and remove existing MQ full Repositories :-
Create a new queue manager on MQ 7.5 Environment on AIX platform
Make a new queue manager as full repos on MQ 7.5 on AIX
Add new mq full repositories queue manager into the existing MQ cluster environment in aix environment.
Ensure that all queue manager cluster objects count sync with old mq full repositories (CPQM1 and CPMQ2) as well as new mq full repositories (CPQMFR001 and CPQMFR002)
At this moment, there will be no partial repository queue manager connect to new MQ full repository queue manager CPQMFR001 and CPQMFR
Ensure that new hardware MQ full repositories CPQMFR001 and CPQMFR002 are visible into all Full Repositories as well as into the partial repositories queue manager.
There will 4 MQ full repositories queue manager in the MQ Cluster and will ensure that all four QM FUll repositories are sync with each other with all MQ cluster objects

Remove CPQM1 and CPQM2 full repositories from the MQ cluster so there will be CPQMFR001 and CPQMFR002 full repositories queue manager available in the MQ cluster
Steps will be follow to remove CPQM1 and CPQM2 full repositories from the MQ cluster :-
1) Alter CPQM1 full repository queue manager to be a partial repository (alter qmgr repos(' ')
2) Suspend CPQM1 Full repository queue manager from the MQ cluster (suspend qmgr cluster(clustername)
3) alter cluster receiver on CPQM1 to take it out of MQ cluster (alter channel(channelname) chltype(clusrcvr) cluster(' ')
4) stop channel of CPQM1 from the cluster
5) delete channel of CPQM1 from the cluster
6) Verify that CPQM1 queue manager are not visible into the CPMQ2, CPQMFR001 and CPQMFR002 full repositories queue manager
7) alter cluster sender to CPQM2 full repository queue manager to be partial repository (alter channel(channel name) chltype(clusrcvr) cluster (' ')
stop channel and delete channel

Note :- At this point cluster has only three full repositories CPMQ2, CPQMFR001 and CPQMFR002 and CPMQ1 is out of cluster.
All partial repositories will be able to function as they have established connection to remaining full repository queue manager.

The same step will be perform to remove CPMQ2 full repository queue manager from the MQ cluster.

Question :-
RESET cluster command need to be execute on remaining full repositories queue manager CPMQ2, CPQMFR001 and CPQMFR002 to take all info about CPMQ1 queue manager from the MQ cluster out?
I think RESET cluster command need to be execute when you have same FR queue manager name on existing MQ cluster and new hardware queue manager full repository?
Is there any steps has been skip as per the best recommendation practice to remove existing MQ full repository and join new MQ full repository from new hardware?

Kindly provide your inputs on this.


Thanks,
MacWag
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Thu Nov 10, 2016 2:18 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7717

https://www.ibm.com/developerworks/community/blogs/messaging/entry/mq_clusters_replacing_or_relocating_full_repositories?lang=en
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Nov 11, 2016 5:44 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

Well looks like you missed a few steps.

Before touching any of the old full repositories you need to change all the PRs to point towards the new FRs.
Now that the PRs have no more pointers to the old FRs you can start looking at removing them from the cluster.

The first operation on the old FRs, after having turned them into PRs, would be to "de-cluster" any queues/topics etc that have been defined on said old FR.

Once all local cluster objects have been removed from the cluster, you can start removing the queue manager (now a PR) from the cluster.

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
mbwagner
PostPosted: Fri Nov 11, 2016 8:28 am    Post subject: Reply with quote

Novice

Joined: 24 Feb 2016
Posts: 17

Thanks Peter & fjp_saper

We do not have any plan to remove the cluster objects from old FRs.
The plan is to only make full repositories on new queue manager on the new server.
Old FRs will be convert into the partial repositories and it will be part of the same MQ cluster with all present cluster objects.

Converted PRs queue manager will be interconnect with new FR queue managers created on new servers.

fjb_saber

As you suggested, we have prepared our plan like below :-

1) Create a new queue manager on MQ 7.5 Environment on AIX platform
2) Make a new queue manager as full repository on MQ 7.5 on AIX
3) Add new server MQ 7.5 full repositories queue manager into the existing MQ cluster environment with MQ 7.0 PRs- aix environment.
5) There will be 4 full repositories interconnect each other in the cluster environment.

6) Ensure that all queue manager cluster objects count sync with old mq full repositories (CPQM1 and CPMQ2) as well as new mq full repositories (CPQMFR001 and CPQMFR002)

7) At this moment, there will be no partial repository queue manager connect to new MQ full repository queue manager CPQMFR001 and CPQMFR002.

Ensure that new hardware MQ full repositories CPQMFR001 and CPQMFR002 are visible into all Full Repositories as well as into the partial repositories queue manager.

9) There will be 4 MQ full repositories queue manager in the MQ Cluster and will ensure that all four QM FUll repositories are sync with each other with all MQ cluster objects.

10) As you suggested, we will create new cluster sender channels on partial repository queue managers to point towards the new full repository queue managers.
Partial repositories will be connect to old FR as well as New FR queue managers.

11) Remove PR queue manager connectivity with old Full Repositories.
Ensure that there will be no direct pointer between PR and Old Full Repositories.

Remove CPQM1 full repositories from the MQ cluster - alter qmgr repos(' ').
stop channel(CLUSTER.CPQM2)
delete channel(CLUSTER.CPQM2)
start channel(CLUSTER.CPQM2)

stop channel(CLUSTER.CPQMFR001)
delete channel(CLUSTER.CPQMFR001)
start channel(CLUSTER.CPQMFR001)

There will be CPQM2, CPQMFR001 and CPQMFR002 full repositories queue manager available in the MQ cluster.

Need to ensure that CPQM2, CPQMFR001 and CPQMFR002 full repositories are sync with each other and all partial repositories queue manager sync with new FRs.

The same steps will be follow to remove CPQM2 old full repository queue manager from the mq cluster.


Questions :-
1) MQ 7.5 full repository and MQ 7.0 partial repository will be compatible in the same MQ cluster?
2) Using above steps there will be no cluster object information delete/miss from the new converted PR queue managers CPQM1 and CPQM2.
Back to top
View user's profile Send private message
exerk
PostPosted: Fri Nov 11, 2016 10:59 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

mbwagner wrote:
Questions :-
1) MQ 7.5 full repository and MQ 7.0 partial repository will be compatible in the same MQ cluster?

Yes.

Also, bear in mind that MQ V7.0 is now out of support and MQ V7.5 has only just a little over a [y]ear of life left in it, so I suggest planning to migrate to MQ V8.0/V9.0 now.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » Moving MQ Cluster Full Repository to new queue manager on ne
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.