| Author |
Message
|
| jfecq |
 Posted: Mon Nov 19, 2012 1:28 am Post subject: MSCS failover with shared folder path |
 |
|
Apprentice
Joined: 24 Sep 2012
Posts: 36
|
Hi,
Due to limitations, I am trying out deploying Windows 2008 failover clustering. However the configuration is that the queue manager resides on a shared folder path.
When I try to put it under MSCS control, it failed with the error 'The specified queue manager is already configured for multi-instance support and cannot be used.'
I wish to clarify that if a qm is created on a shared folder, MQ automatically detects it as multi instance hence unable for MSCS? |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Nov 19, 2012 1:46 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
You have a choice - MSCS or MI. You can't have both together as one thing as MI relies on network drive availability and MSCS relies on 'same' disk availability.
_________________
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 |
|
|
| jfecq |
| Posted: Mon Nov 19, 2012 1:59 am Post subject: |
|
|
Apprentice
Joined: 24 Sep 2012
Posts: 36
|
| Yup I know is either or. So does that means MQ will detect qm created on shared folder is MI, and there is no way to 'turn it off'? Meaning able to use MSCS on shared folder? |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Nov 19, 2012 2:04 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| jfecq wrote: |
| Yup I know is either or. So does that means MQ will detect qm created on shared folder is MI, and there is no way to 'turn it off'? Meaning able to use MSCS on shared folder? |
You cannot use a shared folder for MSCS.
_________________
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 |
|
|
| bruce2359 |
| Posted: Mon Nov 19, 2012 6:25 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| jfecq wrote: |
| So does that means MQ will detect qm created on shared folder is MI? |
No. There is more to creating an MI environment than just simply sharing a disk.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Sep 14, 2020 10:30 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
At the risk of reviving a thread that is nearly 8 years old....
The error dialog "The specified queue manager is already configured for multi-instance support and cannot be used" displayed by amqmclxn (the Windows Failover Cluster Manager MQ resource config dialog) may also be produced by the way parameters are specified in the mqs.ini file.
In reply to previous posts, it doesn't seem to matter whether or not the MQ data dir is part of a Windows Share. Of course the MQ data dir needs to be on a disk drive that is a MSCS cluster resource.
The following works with strmqm & amqmdain to start a qmgr, but is not acceptable to amqmclxn:
| Code: |
QueueManager:
Name=MQTEST1
Prefix=D:\MQSeries (same as the MQ DefaultPrefix data dir)
Directory=MQTEST1
DataPath=F:\MQData\qmgrs\MQTEST1
InstallationName=Installation1 |
This works with strmqm, amqmdain, amqmclxn:
| Code: |
QueueManager:
Name=MQTEST1
Prefix=F:\MQData
Directory=MQTEST1
InstallationName=Installation1 |
FWIW, I'm using MQ 9.0 on Windows 2016.
HTH
_________________
Glenn |
|
| Back to top |
|
|
|
|
