| Author |
Message
|
| gdrucker |
 Posted: Tue Feb 06, 2007 10:41 am Post subject: Migration to MQ V6.0.2 - MSCS |
 |
|
Apprentice
Joined: 17 Jun 2005
Posts: 36
Location: New York
|
So, I have done much testing of the upgrade from MQ V5.3 to V6 and aside from migrating SSL certs, the migration was very smooth. And I have gotten past my SSL cert issues.
The question is how to migrate while running on Microsoft clustering (Active / Passive). I think the steps start something like this:
1 - Use SAVEQMGR to save all objects
2 - Shutdown qmgr (use cluster admin to take MQ resource offline)
3 - Use hamvmqm command to move data and log files to local drive
4 - Perform MQ upgrade / load Refresh Pack 2
At the point, do I copy data/log files back to the shared drive, go to node 2 and start over with the same procedure?
I have searched through the Migration guide, System Admin guide and have not found the answers I am looking for.
I'm hoping to benefit from someones prior experience with upgrading MQ in the MSCS world.
Thank you. |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Feb 06, 2007 1:51 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I suggest upgrading both nodes before migrating it back to the shared drive, you wouldn't want it attempting to fail over to the upgrading node.
_________________
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 |
|
|
| gdrucker |
| Posted: Wed Feb 07, 2007 6:31 am Post subject: |
|
|
Apprentice
Joined: 17 Jun 2005
Posts: 36
Location: New York
|
| As per IBM, the data and log files are not updated during the upgrade procedure and their is no reason to remove them from MSCS control. So, maybe I am complicating this more than I need to. Well, back to testing... |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Feb 07, 2007 6:55 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Personally, and for reasons already stated, I would still migrate the queue manager from MSCS storage and upgrade each node in turn before returning the queue manager to MSCS storage.
_________________
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 |
|
|
| BBM |
| Posted: Thu Feb 15, 2007 6:10 pm Post subject: |
|
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
We're about to embark on the same process also...
If we do migrate the data to to the local drive and upgrade each node in that way, that would imply that we would have to:
Migrate data from shared drive to local drive of 1st node
Upgrade 1st node
Migrate data from 1st node to shared drive
Migrate data from shared drive to local node of 2nd node
Upgrade 2nd node
Migrate data from 2nd node to shared drive
Surely this is a bit of a lengthy process... - does anyone have the official IBM view as I'm more than little surprised that they didn't deem it necessary to document this!
BBM |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Feb 16, 2007 7:18 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| BBM wrote: |
Migrate data from shared drive to local drive of 1st node
Upgrade 1st node
Migrate data from 1st node to shared drive
Migrate data from shared drive to local node of 2nd node
Upgrade 2nd node
Migrate data from 2nd node to shared drive |
Migrate data to shared drive
Would work for me. Can't see why you'd want to migrate across to the other node then upgrade as I view this a reverse process of the initial install and configuration.
_________________
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 |
|
|
| gdrucker |
| Posted: Tue Feb 20, 2007 2:02 pm Post subject: |
|
|
Apprentice
Joined: 17 Jun 2005
Posts: 36
Location: New York
|
The problem comes into play when it is time to schedule the migration of the SSL certificates. MQ logs an error because it cannot access the shared drive. It may have to be done manually after the upgrade. Still testing...
As per IBM:
Under WMQ 5.3 SSL support under MSCS required identical certificate
stores, in the same relative locations, on both nodes. Under v6 these
will be replaced by a single (GSKit) key store on the shared drive. At
the point where the prepare Wizard failed it was trying to set up the
migration at the next startup of the qmgr - but was unable to as the shared drive was unavailable.
I agree that migrating to the local drive maybe extreme and I am trying to upgrade without having to go down that path. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Feb 20, 2007 3:15 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
If the Key Store is on local drive the hamvmqm command will then move everything back, which just leaves the SSLKEYR attribute of the qmgr to be changed.
I would still recommend migrating back to 'local' disk as the hassle involved may be far less than a total qmgr rebuild or having to try and remove/re-install WMQ as a worst case.
_________________
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 |
|
|
|
|
