| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| mscs cluster |
« View previous topic :: View next topic » |
| Author |
Message
|
| saneben |
 Posted: Sun Feb 14, 2010 12:07 pm Post subject: mscs cluster |
 |
|
Voyager
Joined: 04 Apr 2004
Posts: 96
|
Hi,
I have set up a MSCS cluster on windows 2003 and it is working fine on an active /passive mode with one queue manager with a virtual ip address and stared storage with is working fine.
Now since environment is running on MQ V5.3, I need to upgrade this to MQ V6.0 only now due to application dependency.
I would like to like know what steps to flollow to upgrade.
Like stop the cluster service, upgarde the active/passive node first
Any URL or doc is appricated
Regards |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Feb 14, 2010 12:57 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Take a look at the WMQ Quick Beginnings manual for Windows.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| shruthi |
| Posted: Fri Feb 19, 2010 1:03 pm Post subject: |
|
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
we have done the upgrade sucessfully with Below steps & with downtime:
For 'migration of an MSCS cluster from WebSphere MQ version 5.3 to
version 6'.
Ensure that the cluster service and the MQ series service is
stopped on the node which is being migrated.
Customer should be able to migrate MQ on both the nodes simultaneously if MQ and cluster service can be stopped on both the nodes.
Below are for no downtime(i didnt implement them):
1. Perform a full back-up of any queue managers including any SSL keystores defined.
2. Modify the possible owners of the MQ resource to encompass the Active node/s only. This is to prevent the MQ resource from experiencing an unexpected failover to the node currently being migrated.
3. Ensure that the group containing the MQ resource is currently on a different node to that which is being upgraded. This should include any applications connecting to the queue manager.
4. Stop the cluster service on the node being migrated. This step is necessary to clear the MSCS cache of any MQ dlls it has registered.
5. Migrate the Passive node by following the standard instructions in the Quick Beginnings guide. Apply the required maintenance level.
6. Start the cluster service on the Passive node.
7. On the next node to be migrated, ensure that the resource is not online on this node. If this is an Active node, take the resource offline on this node.
8. Modify the possible owners of the MQ resource to exclude this node. For clusters with more than 2 nodes, please refer to the additional considerations below.
9. Move the group containing the MQ resource to a possible owner on one of the other nodes and bring it online on that node.
10. Repeat steps 4-9 as necessary for the remaining node/s. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Feb 19, 2010 1:22 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I reboot between steps 5 and 6.
I reboot, therefore I am....on Windows.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
