| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Migrating MSCS queue managers from V5.3 to V6(urgent) |
« View previous topic :: View next topic » |
| Author |
Message
|
| shruthi |
 Posted: Tue Dec 02, 2008 5:50 pm Post subject: Migrating MSCS queue managers from V5.3 to V6(urgent) |
 |
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
Hi Guys,
We are planning to do MQ upgrade from V 5.3 to V6.0.2.4 on MSCS Cluster.In our case we have a 2 node cluster Active/Passive scenario.
I dont see anything in manuals ,steps involved in upgrading for Windows cluster .
Question is how to migrate qmgrs on Microsoft clustering (Active / Passive).
I assume following steps:
1 - Use cluster admin to take MQ resource offline (Shutdown qmgr )
2 - Perform MQ upgrade & load Refresh Pack 4 on both Nodes
3 - After Fix installations on both nodes bring MQ resource online on one of the node(Start Qmgr).
Can you please let us know if we are doing correct. |
|
| Back to top |
|
 |
| shruthi |
| Posted: Fri Dec 05, 2008 11:50 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
|
| Back to top |
|
|
| shruthi |
| Posted: Mon Dec 08, 2008 1:27 pm Post subject: Got it , we have done the upgrade sucessfully |
|
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
Got it , we have done the upgrade sucessfully.
Below are the steps with downtime:( i did this)
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 for with no downtime:
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
