| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| V6 to V7 Version upgrade - Primary FR upgrade |
« View previous topic :: View next topic » |
| Author |
Message
|
| skydoor |
 Posted: Tue Mar 02, 2010 12:54 am Post subject: V6 to V7 Version upgrade - Primary FR upgrade |
 |
|
Apprentice
Joined: 24 Jul 2007
Posts: 43
Location: Cape Town
|
I am planning a version upgrade of our entire central system and I have a question regarding the upgrade of the Primary FR.
We currently have two FR's called gateway1 and gateway2. All the PR's point to gateway1 for cluster information. I was hoping to add two V7 FR's and remove the old V6 FR's and leave it at that but then realized that all the PR's are pointing at gateway1.
It is impractical to add a new primary FR and modify all the PR's cluster pointers to the new FR as there are too many of them to do practically.
An added complication is that I want to move our platforms from a Windows based platform to a Linux based platform. If the migration option is the only option, this is not possible.
I have two options here: 1. Migrate the primary FR from V6 to V7 - dangerous as a failure in the upgrade might kill the FR.
2. Replace the primary V6 FR with a primary V7 FR and wait till it updates the cluster information from the secondary V6 FR.
I would appreciate any comments, experiences or pointers on the matter.
Documents found and read so far:
http://www.ibm.com/developerworks/websphere/library/techarticles/0910_beardsmore/0910_beardsmore.html
_________________
The answer to the question is 42 |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Mar 02, 2010 5:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Even if you have only defined explicit clussdrs that connect all your qmgrs to gateway1 and defined no explicit clussdrs to gateway2, all of your qmgrs still know about and will use gateway2 if gateway1 is unavailable. |
|
| Back to top |
|
|
| skydoor |
| Posted: Tue Mar 02, 2010 6:28 am Post subject: |
|
|
Apprentice
Joined: 24 Jul 2007
Posts: 43
Location: Cape Town
|
-> mqjeff
This is the case, all the PR's are pointed with explicit clussdr's to the gateway1. If I understand you correctly, I can remove the primary FR and replace it with an identical queue manager that is the new primary FR. In the time it takes to do the swap, the PR's will reference the secondary FR.
The question I have is, will the PR's accept the new FR, or will they require intervention, like for instance resetting the counts? I know you have to do this on a distributed system, but I have not had to do that in a clustered system and I don't know if it is a requirement.
I have a gut feeling that this will not work. I feel that the PR's will have to be modified to point the clussdr's to the new primary FR and restart the channels.
_________________
The answer to the question is 42 |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 02, 2010 8:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| skydoor wrote: |
| The question I have is, will the PR's accept the new FR |
| skydoor wrote: |
| or will they require intervention, like for instance resetting the counts? |
| skydoor wrote: |
| I know you have to do this on a distributed system, but I have not had to do that in a clustered system and I don't know if it is a requirement. |
One of the advantages of clustering.
| skydoor wrote: |
| I have a gut feeling that this will not work. I feel that the PR's will have to be modified to point the clussdr's to the new primary FR and restart the channels. |
Yes it will and no they won't.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Mar 02, 2010 9:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| skydoor wrote: |
| The question I have is, will the PR's accept the new FR |
| skydoor wrote: |
| or will they require intervention, like for instance resetting the counts? |
|
If it is the *same* queue manager, you are correct. If it is a *new* qmgr with a *different* name, you are correct. If it is a *new* qmgr with the *same* name...
skydoor - You're going to have to do *something* on all qmgrs. The *best* thing is to create a new qmgr with a new name, add it as an FR to the cluster (i.e. connect it to gateway2), and then run a script on all qmgrs that deletes the explicit clussdr to gateway1 and adds new explicit clussdrs to gateway2 and the new qmgr and then starts them. |
|
| Back to top |
|
|
| skydoor |
| Posted: Tue Mar 02, 2010 11:02 pm Post subject: |
|
|
Apprentice
Joined: 24 Jul 2007
Posts: 43
Location: Cape Town
|
Thanks Vitor & mqjeff - your input is much appreciated - This has resolved the problem for me.
_________________
The answer to the question is 42 |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
