|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Legato CoStandby for failover on Win2K |
« View previous topic :: View next topic » |
Author |
Message
|
Cliff |
Posted: Tue Sep 25, 2001 6:23 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001 Posts: 145 Location: Wiltshire
|
Hello, all.
If anone has any experience of using Legato software for failover between two Win2K boxes running MQ then I would be delighted to hear from them.
We have an OS/30 app sending messages to a remote queue which lurks on a Win2K box at a geographically remote site, supporting a workflow application and message sequence is critical. Because of this, it has been decided to use a single queue manager and this Legato software (I only found out about it this morning!) to control failover between a a main and a backup box. Legato apparently works by mirroring between D drives (it doesn't touch C drives, it seems) so when Box1 falls over and Box2 kicks in, all your data is as it should be and everything works as if by magic. That's the theory, anyway.
We have installed MQ with program data on C and logs and queue data on D on both machines, created same-name qmgrs, queues and channels, and sent a persistent message from a third box to Box1. Failover to Box2, and no messages. Had to reset channel sequence numbers, of course. What's going on????
I would note that MQ has been uninstalled and reinstalled on both machines. We can send messages to Box1 or Box2 individually but I expected message data to be there after failover. Also, if I define a new queue it is not apparently 'there' on the second machine after failover.
I am clearly missing something! Any suggestions, pointers towards documentation etc warmly welcomed.
Yours, baffled,
Cliff |
|
Back to top |
|
 |
Cliff |
Posted: Tue Sep 25, 2001 8:20 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001 Posts: 145 Location: Wiltshire
|
I now have answers to at least some of my problems!
A queue manager did not get deleted cleanly, so MQ helpfully created another in the file tree called QMname.000 which you can't, of course, see through the command line or MQ Explorer. Legato was actually mirroring my files, but MQ Explorer was looking at the files for the non-existent queue manager QMName.000. I discovered this via the dspmqfls command which shows the actual filepaths to the various queue files.
Oh well, you learn something new every day, eh?
Watch out for those incomplete deletes -
Cliff |
|
Back to top |
|
 |
msantos007 |
Posted: Wed Apr 27, 2005 5:36 am Post subject: You Have To Change Data and Log Area to the storage disk |
|
|
Voyager
Joined: 20 Dec 2004 Posts: 78
|
To get your MQ data in the other cluster node, you'll to change the data and log folders to the Storage disk(or shared disk) of the cluster, using the command:
hamvmqm /m qmname /dd "<X>:\WebSphere MQ" /ld <X>:\WebSphere MQ\log"
where <X> is the letter of your shared disk _________________ Maximiliano R. A. Santos
IBM Websphere MQ V6.0 Certified System Administrator
IBM Websphere MQ V5.3 Certified Solution Developer |
|
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
|
|
|
|