| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Webpshere MQ 7.0.1 running on MSCS . |
« View previous topic :: View next topic » |
| Author |
Message
|
| blorro |
 Posted: Fri Aug 29, 2014 3:57 am Post subject: Webpshere MQ 7.0.1 running on MSCS . |
 |
|
Acolyte
Joined: 09 Jan 2014
Posts: 57
Location: Sweden
|
Running two QueueManagers in production on two Physical Windows server nodes clustered via MSCS and with Linear logging .
Now, new servers in our Businesspartners DC will be delivered and we are looking at migrating our QueueManagers to the new servers.
Looking for "Best practices" migrating Microsoft Clustered Windows Server QueueManagers with Linear Logging.
"Intro to Websphere MQ Migration" found in the IBM Infocenter, and digesting those pages but any more hints or "dont forget this" would be nice to have from more seasoned pros =) |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Aug 29, 2014 4:22 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Build the new servers in parallel with the latest software.
Create a new queue manager on the new server with a similiar but different name so that you don't have 2 QMs on the network with the same name.
Use MS03 or dmpmqcfg to export all MQ objects off the old and onto the new.
Test this new system thoroughly.
You can do all this during normal hours and take as much time as you want because the old system is still up and running.
When it makes sense, stop traffic to the old QM, have the app drain all the queues, stop the QM on the old system, have the app start up talking to the new queue managers on the new servers.
If anything goes wrong, the old system is waiting on the side for an easy fall back.
This is my preferred method - building a new system in parallel and then cutting over. It offers an easy fall back, allows you to build the new system with the latest versions of software, and you can build the new system during normal hours and at a normal pace.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Aug 29, 2014 8:52 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| PeterPotkay wrote: |
Use MS03 or dmpmqcfg to export all MQ objects off the old and onto the new.
|
There are some well documented problems with dmpmqcfg so you would be advised to use amqoamd AS WELL as dmpmqcfg to completely document all the objects in the queue manager.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| blorro |
| Posted: Thu Sep 04, 2014 12:40 am Post subject: |
|
|
Acolyte
Joined: 09 Jan 2014
Posts: 57
Location: Sweden
|
Thank you for your replies.
Now, since we got thousands of message flows on this particular QueueManager it would be great to be able to preserve QueueManager name(s). I'm guessing this is impossible to achieve ?
Another thing that has come up is the usage of MSCS or running Single-node instead due to the complexity of running two QueueManagers on two Clusternodes.
Pros with clustering is patching of Windows obviously but finding other pro's t is not that easy.
Almost getting the feeling that uptime is decreased when running MSCS at times.
Thoughts on running clustered vs single vm nodes ? |
|
| 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
|
|
|
|
