| Author |
Message
|
| career |
 Posted: Thu Nov 08, 2007 9:19 am Post subject: Questions on High Avialability |
 |
|
Apprentice
Joined: 09 Jul 2007
Posts: 36
|
Hi all,
I was going thru this support pack mc6a for HA using Veritas Cluster Server . I have few questions and would greatly appreciate if some would make my understanding clear.
For active passive configuration
I will be having
/var on the internal disk and
/MQHA/<qmgr>/data on shared disks
/MQHA/<qmgr>/log on shared disks
now i have few questions
1) should i have to use on the primary node
export MQHAFSDATA="/MQHA/<qmgr>/data"
export MQHAFSLOG="/MQHA/<qmgr>/log"
before hacrtmqm <crtmqm parameters> or after?
are those export commands enough to create the log and data files on the shared disk? as i have read in Veritas High Availability Agent 5.0 for WebSphere MQ Installation and Configuration Guide AIX, HP-UX, Linux, Solaris, that we need to create seperate files on the shared disk and copy the log&data files from local system to shared disk and then delte them from local disk.
2) on the second node ( passive) should i have to creat the queue manager or just use halinkmqm command?
with out creating the QM on second node how can the fail over possible ( as is is not mentioned on mc6a support pac) my understanding is tht we will create Qm but stop it and run the halinkmqm so tht only log and data files on the shared disk will be connected to QM is it right?
I would greatly appreciate ur reply
Thanks. |
|
| Back to top |
|
 |
| LMD |
| Posted: Thu Nov 08, 2007 3:07 pm Post subject: |
|
|
Acolyte
Joined: 30 Oct 2002
Posts: 56
Location: Paris - France
|
hi,
you should export MQHAFSDATA and MQHAFSLOG before hacrtmqm.
if not exported, hacrtmqm will complain ...
On the second node, just run halinkmqm, copying and pasting the parameters displayed and the end of hacrtmqm.
Also (not mentionned in the doc) you installation must allow "su" in scripts.
HTL, LMD.
_________________
lmd_at_demey-consulting.fr - http://demey-consulting.fr - Paris, France.
WMQ, WAS & IIB Certified.
#IBMChampion |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Nov 09, 2007 5:42 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
MC6A was superseded by MC91.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Nov 09, 2007 5:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| JosephGramig wrote: |
| MC6A was superseded by MC91. |
Only for v6...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| career |
| Posted: Fri Nov 09, 2007 6:03 am Post subject: |
|
|
Apprentice
Joined: 09 Jul 2007
Posts: 36
|
Hi Joseph, LMD and others,
I have gone thru MC91. no where it was given abt what should be done on the second node (passive) should i have to simply run halinkmqm on the second node or should i have to creat a second queue manger ( riplica of primary node QM) and then run halinkmqm.....???? How would second node serve application without QM in case of primary failure??
please suggest... |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Nov 09, 2007 6:20 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Hmmm, I read it too (recently). I recall that it did say to just run the halinkmqm command. Nowhere did it say to create the QMGR again. Look on page 10 list item 8.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| career |
| Posted: Fri Nov 09, 2007 6:38 am Post subject: |
|
|
Apprentice
Joined: 09 Jul 2007
Posts: 36
|
hi joseph and others,
quoted as in mc6a
"Internally, hacrtmqm uses a script called halinkmqm to relink the subdirectories used for IPC keys and create a symlink from /var/mqm/qmgrs/<qmgr> to the /MQHA/<qmgr>/data/qmgrs/<qmgr> directory. As shown at the end of hacrtmqm, you need to run halinkmqm on the cluster servers which will act as standby servers for this queue manager. Do not run halinkmqm on the server on which you created the queue manager with hacrtmqm - it has already been run there. The halinkmqm command will create the necessary symlinks and will insert a stanza for the queue manager into the mqs.ini file."
in the above para
" Do not run halinkmqm on the server on which you created the queue manager with hacrtmqm - it has already been run there."
"hacrtmqm uses a script called halinkmqm to relink the subdirectories used for IPC keys and create a symlink from /var/mqm/qmgrs/<qmgr> to the /MQHA/<qmgr>/data/qmgrs/<qmgr> directory"
now tht halinkmqm links /var/mqm/qmgrs/<qmgr> (which is on the primary node) to /MQHA/<qmgr>/data/qmgrs/<qmgr> ( which is on shared disk) with out QM on secondary node how can QM talk to logs and data that are on shared disk in case of failure??
please suggest..... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Nov 09, 2007 6:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
A queue manager is not an object that exists outside of the files in those file systems. Except in the sense that it's a set of processes.
That is, everything that defines the qmgr is contained in those files.
Except for the pieces that exist in mqs.ini and a couple of other registry type things under /var/mqm... that halinkmqm creates or adjust for you.
If you want to understand this better, you should read the halinkmqm script and the hacrtmqm script.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| career |
| Posted: Fri Nov 09, 2007 8:07 am Post subject: |
|
|
Apprentice
Joined: 09 Jul 2007
Posts: 36
|
Hi jefflowrey,
I just want to make to my self this point clear....So you say tht there is no need to creating QM on the second node ( passive). i have to install MQ on and I have to just run the halinkmqm on the passive node right??
and
export MQHAFSDATA="/MQHA/<qmgr>/data"
export MQHAFSLOG="/MQHA/<qmgr>/log"
( i mean using those environment variavles we can move log and data files to storage disks)
will create log files and data files on Storage Disk. There is no need to copy the log files and data files from the node to storage system and create a symbolic link.
Please suggest....this is quite confusing me..... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Nov 09, 2007 8:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| career wrote: |
| I just want to make to my self this point clear.... |
| JosephGramig wrote: |
| just run the halinkmqm command. Nowhere did it say to create the QMGR again. Look on page 10 list item 8. |
| LMD wrote: |
| just run halinkmqm |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Nov 09, 2007 12:49 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Hmmm. I'm assuming you are using WMQ v6.0 because 5.3 is out of support. Your account says 'Novice' and I hope that is because you just created it and that you are not new to WMQ.
You have to read the document carefully and it is intended for experienced WMQ Administrators. If you are not an experienced WMQ Administrator, then you should seek help from someone who has setup WMQ on one HA platform (it does not matter which as HA is very much the same on all platforms).
It is not hard to do but it does require attention to detail. Those who support it need to know it is an HA setup and that they need to keep both the machines as identical as possible. Because the file systems will be shared between the two machines, make sure the UID and GID of all the IDs and groups on the machines are identical. If you don't know why I'm saying this, seek help.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
|
|
