| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Stopping FR Qmgr |
« View previous topic :: View next topic » |
| Author |
Message
|
| ramesh80 |
 Posted: Tue Jan 08, 2019 1:50 am Post subject: Stopping FR Qmgr |
 |
|
Novice
Joined: 22 Oct 2018
Posts: 20
|
HI,
I have 4 qmgrs QM1,QM2,QM3,QM4 on 4 different aix servers in prod env.
All 4 of them are in a cluster QM1 and QM2 are FR's and QM3,QM4 are PR's
We have a maintenance on all the 4 servers, 2 servers on one day and other 2 on other day.
QM1 and QM3 servers have maintenance on one day.
I wanted to know how do we bring down the qmgrs.
Please tell me if the below steps are correct
1.suspend QM3 and QM1 from the cluster
2.stop qmgrs QM3 and QM1
after maintanence ,
3.start qmgrs
4.resume qmgrs
are these steps enough or am i missing something?
What else do we need to do, to bring back the cluster as it is before?
I wanted to be sure as i have to do it in Prod env. |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Jan 08, 2019 1:58 am Post subject: Re: Stopping FR Qmgr |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| ramesh80 wrote: |
| ...I wanted to be sure as i have to do it in Prod env. |
So practice in a non-Production environment first. The Knowledge Centre, appropriate to your version of MQ, details the steps necessary to perform maintenance.
_________________
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 |
|
|
| hughson |
| Posted: Tue Jan 08, 2019 2:08 am Post subject: Re: Stopping FR Qmgr |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| ramesh80 wrote: |
Please tell me if the below steps are correct
1.suspend QM3 and QM1 from the cluster
2.stop qmgrs QM3 and QM1
after maintanence ,
3.start qmgrs
4.resume qmgrs
are these steps enough or am i missing something? |
Looks fine to me, although I would add between step 1 and step 2:-
1a. Wait until message traffic reduces down to as low as possible.
You want to be sure that all messages that can be routed to an alternate queue manager have done so before stopping the queue manager. That's what SUSPEND says. If you have some queues only hosted on one queue manager, they will always go to that queue manager, but if you have queues hosted in multiple places, give the cluster a chance to choose that queue manager. Monitor the messages being sent across your cluster channels to the suspended queue managers, and when it all but dries up, then you can stop them and have much less effect on the clustered applications, than if you stopped them immediately after the suspend.
Further Reading
IBM Knowledge Center: Maintaining a queue manager
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| ramesh80 |
| Posted: Tue Jan 08, 2019 3:53 am Post subject: |
|
|
Novice
Joined: 22 Oct 2018
Posts: 20
|
| Thanks Exerk and Hughson for your suggestions |
|
| 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
|
|
|
|
