| Author |
Message
|
| aditya.aggarwal |
 Posted: Tue Sep 22, 2009 6:10 am Post subject: |
 |
|
Master
Joined: 13 Jan 2009
Posts: 252
|
| Quote: |
| We looked at the VCS MQ agent and decided to stick with MC91, mainly because VCS did not have a WMB agent and I didn't want to mix solutions, so we went with MC91 + IC91. |
We are not using Broker. I do agree that With Broker MC91+IC91 is the best solution.
PeterPotkay wrote:
| Quote: |
| And again, good luck with your MQ upgrades as they are going to be more complicated now. I am not 100% sure, but I think that the MQ upgrade is going to want /var/mqm as well. |
yes MQ upgrade need /var/mqm. We have a backup of /var/mqm directory and we can put it back while upgrading the MQ.
| Quote: |
| And it needs the QM down. You are going to have to fail the QM over and leave it down just to upgrade the passive node. And then fail the group back and leave the QM down again to upgrade the normally active. Not very H.A., huh? |
not agree. Steps of upgrades are listed below.
1. /var/mqm is mounted at Node A and Node B is passive.qmgr is running at Node A
2. Put the /var/mqm backup on the Node B.
3. upgrade MQ at Node B and take backup of /var/mqm and remove it from node B.
4. mount /var/mqm at Node B and Node A is passive. qmgr is running at Node B
5. Put the /var/mqm backup on the Node A.
6. upgrade MQ and qmgr at Node A. qmgr was created on the Node A.
7. Stop qmgr Node and unmount the /var/mqm, /var/mqm/logs at Node B and mount the /var/mqm and /var/mqm/logs at Node A. [hardly 1-3 minutes]
8. Start qmgr.
9. remove /var/mqm after taking backup at node B.
| Quote: |
| With MC91 we can upgrade the passive node anytime, take a 1 minute outage to fail the QM over and then upgrade the other node while the QM runs. |
with VCS agent donwtime is 1-3 minutes. not much difference. |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Sep 22, 2009 6:23 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| aditya.aggarwal wrote: |
...Steps of upgrades are listed below.
1. /var/mqm is mounted at Node A and Node B is passive.qmgr is running at Node A
2. Put the /var/mqm backup on the Node B.
3. upgrade MQ at Node B and take backup of /var/mqm and remove it from node B.
4. mount /var/mqm at Node B and Node A is passive. qmgr is running at Node B
5. Put the /var/mqm backup on the Node A.
6. upgrade MQ and qmgr at Node A. qmgr was created on the Node A.
7. Stop qmgr Node and unmount the /var/mqm, /var/mqm/logs at Node B and mount the /var/mqm and /var/mqm/logs at Node A. [hardly 1-3 minutes]
8. Start qmgr.
9. remove /var/mqm after taking backup at node B. |
Seems incredibly complicated to me, more so than removing a service group from VCS control and upgrading node-by-node, and a potential recipe for disaster if someone tries to mount the file system while you're doing the upgrade.
When's the wake?
_________________
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 |
|
|
| PeterPotkay |
| Posted: Tue Sep 22, 2009 6:43 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| aditya.aggarwal wrote: |
| Quote: |
| And it needs the QM down. You are going to have to fail the QM over and leave it down just to upgrade the passive node. And then fail the group back and leave the QM down again to upgrade the normally active. Not very H.A., huh? |
not agree. Steps of upgrades are listed below.
1. /var/mqm is mounted at Node A and Node B is passive.qmgr is running at Node A
2. Put the /var/mqm backup on the Node B.
3. upgrade MQ at Node B and take backup of /var/mqm and remove it from node B.
4. mount /var/mqm at Node B and Node A is passive. qmgr is running at Node B
5. Put the /var/mqm backup on the Node A.
6. upgrade MQ and qmgr at Node A. qmgr was created on the Node A.
7. Stop qmgr Node and unmount the /var/mqm, /var/mqm/logs at Node B and mount the /var/mqm and /var/mqm/logs at Node A. [hardly 1-3 minutes]
8. Start qmgr.
9. remove /var/mqm after taking backup at node B.
|
You need to take a QM outage to get a good back up of /var/mqm.
Everytime you start the QM it will change things in /var/mqm, yet your plan calls for overlaying those changes multiple times. I suppose you could leave the QM down the entire time.
You got a lot more than a 1-3 minutes of downtime and a whole lot of steps that open you for potential file coruption.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Tue Sep 22, 2009 7:07 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
aditya.aggarwal wrote:
...Steps of upgrades are listed below.
1. /var/mqm is mounted at Node A and Node B is passive.qmgr is running at Node A
2. Put the /var/mqm backup on the Node B.
3. upgrade MQ at Node B and take backup of /var/mqm and remove it from node B.
4. mount /var/mqm at Node B and Node A is passive. qmgr is running at Node B
5. Put the /var/mqm backup on the Node A.
6. upgrade MQ and qmgr at Node A. qmgr was created on the Node A.
7. Stop qmgr Node and unmount the /var/mqm, /var/mqm/logs at Node B and mount the /var/mqm and /var/mqm/logs at Node A. [hardly 1-3 minutes]
8. Start qmgr.
9. remove /var/mqm after taking backup at node B.
Seems incredibly complicated to me, more so than removing a service group from VCS control and upgrading node-by-node, and a potential recipe for disaster if someone tries to mount the file system while you're doing the upgrade.
When's the wake?
I agree. ..Those were only high levle steps... We have these points in mind and work with unix team in sync while doing upgrade....
Cheers,
Aditya |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Tue Sep 22, 2009 7:11 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
Peter Potaky wrote:
| Quote: |
| You need to take a QM outage to get a good back up of /var/mqm. |
Agree.. we have that already in place for Node A.
| Quote: |
| Everytime you start the QM it will change things in /var/mqm, yet your plan calls for overlaying those changes multiple times. I suppose you could leave the QM down the entire time. |
no it will be down at Step 7
| Quote: |
| You got a lot more than a 1-3 minutes of downtime |
yep... Agree..
| Quote: |
| a whole lot of steps that open you for potential file coruption |
not agree...please explain how this will damage the files... if upgrade performed carefully.
Cheers,
Aditya |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Sep 22, 2009 7:23 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| aditya.aggarwal wrote: |
| Peter Potaky wrote: |
I am not related to the former NY Governor.
| aditya.aggarwal wrote: |
| Quote: |
| a whole lot of steps that open you for potential file coruption |
not agree...please explain how this will damage the files... if upgrade performed carefully.
|
Back this up, back that up, mount this, mount that, unmount here, back up over there, in the middle of the night, in a tight change window. Like I said, good luck with your upgrades. It can work. I can also walk a tightrope over a cage of lions if I perform carefully. I'd rather not have to if there is a better way! H.A. solutions are typically measured in minutes of downtime per year. You are using a lot of minutes for each MQ upgrade.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Thu Sep 24, 2009 8:15 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
I agree it is risky... will discuss this with our unix team...
but question is still unanswered :
is there any file which correlate the MQ installation with /opt/mqm and /var/mqm ? if yes what is the file name and why dspmqver command need that file to display software version?
cheers,
Aditya |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Sep 24, 2009 1:38 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| aditya.aggarwal wrote: |
I agree it is risky... will discuss this with our unix team...
but question is still unanswered :
is there any file which correlate the MQ installation with /opt/mqm and /var/mqm ? if yes what is the file name and why dspmqver command need that file to display software version?
cheers,
Aditya |
And this question is also unanswered - have you checked that what you're doing is a vendor-supported 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 |
|
|
|
|
