| Author |
Message
|
| muralihegde |
 Posted: Mon Jul 15, 2013 7:00 am Post subject: File System mount point change for existing queue managers |
 |
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Default installation and configuration of MQ Queue Managers on Unix platform would have the following folder structure.
/var/mqm
This hosts all the queue managers folders like
/var/mqm/qmgrs/TESTQMGR1
/var/mqm/qmgrs/TESTQMGR2
And the file system mount points would be /var/mqm
/var/mqm/log
This hosts all the queue managers log folders like
/var/mqm/log/TESTQMGR1
/var/mqm/log/TESTQMGR2
And the file system mount points would be /var/mqm/log
There is a plan to create dedicated file systems for each of the queue managers and mount the directories for each of these queue managers on the individual file systems.
That is we will have new file systems created and mounted as
/var/mqm/qmgrs/TESTQMGR1
/var/mqm/qmgrs/TESTQMGR2
/var/mqm/log/TESTQMGR1
/var/mqm/log/TESTQMGR2
There is no change in the directory structure, but the underlying file system mount points are different and this change would involve mounting the existing folders on to new file systems.
This would involve at the minimum, shutting down the queue managers during the file system mounting and then starting them.
But the concern or the question is does this change need the queue managers to be deleted and re-created? Or a simple shut down during the change and restart would do? |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Jul 15, 2013 7:18 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Are you cloning the existing MQ data into the new filesystems?
Since there may be file locks and so on, you should stop the QM, clone the data to the new filesystem, mount it to replace the old one, start the QM.
Alternatively update QM.INI to reference new data/log locations, which would be my preference, rather than overlay the current path.
Either way you shouldn't move a running QM. |
|
| Back to top |
|
|
| muralihegde |
| Posted: Mon Jul 15, 2013 7:23 am Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
| These are for the existing queue managers. The directory structure would still be the same. But only the underlying mount point will be different, i.e during this change, the directory would not be available. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jul 15, 2013 7:36 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I repeat - you can't move running QMs. It's like trying to change the oil in a car with the engine running.
Directory contain files, MQ uses files for queues and other objects. All these must be copied and the permissions preserved. Using tar can do this. |
|
| Back to top |
|
|
| muralihegde |
| Posted: Mon Jul 15, 2013 8:00 am Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
| Sure. The Queue Managers will certainly be stopped. Also as you suggested, we will also advise to take the back up of the file systems. But do you foresee if we end up deleting and creating the queue manager itself with its objects? |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jul 15, 2013 8:08 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
If you mean do you have to re-create the QM to move the data and log to a new location - no.
Why would I tell you a method that doesn't work?
The way I would do it - is as follows.
1. Get the new file systems ready and mounted with correct ownership for mqm.
2. Stop the QM.
3. Tar up the existing data and log directories (tar -cvf)
4. Untar them to the new locations (tar -xvf)
5. Edit the mqs.ini and relevant qm.ini file to change the data and log location references.
6. Start the QM.
7. When happy with results - remove the old data and log directories.
Test all this in a play pen environment first.
This assumes you are using the v7 datapath and logpath keywords in the configuration files.
The "old" way to redirect the location to a new path would be to use symlinks from /var/mqm/qmgrs |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jul 15, 2013 8:37 am Post subject: Re: File System mount point change for existing queue manage |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| muralihegde wrote: |
There is a plan to create dedicated file systems for each of the queue managers and mount the directories for each of these queue managers on the individual file systems. |
Why? For what purpose? What problem are you trying to solve?
_________________
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 |
|
|
| Tibor |
| Posted: Mon Jul 15, 2013 11:34 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
I agree with bruce2359, it is not really clear for me, what the goal is for creating individual file systems for every qmgr?
By the way, I would prefer using symlink (soft links) from /var/mqm/ filesystem to hacking config files. |
|
| Back to top |
|
|
| muralihegde |
| Posted: Mon Jul 15, 2013 11:37 pm Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
| Trying to avoid file system full scenario due to queues filling up on one queue manager causing damage to other queue managers.. |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Jul 15, 2013 11:39 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| muralihegde wrote: |
| Trying to avoid file system full scenario due to queues filling up on one queue manager causing damage to other queue managers.. |
OK, it can works, but using a monitoring / alerting system is slightly more sophisticated solution 
Anyway, handling multiple (superfluous) mounts is a headache for sysadmins. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 16, 2013 4:30 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| muralihegde wrote: |
| Trying to avoid file system full scenario due to queues filling up on one queue manager causing damage to other queue managers.. |
Exactly what errors are you seeing? Which qmgr(s)? Exactly what is filling the filesystem? Are you certain it's an mq application?
_________________
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 |
|
|
| mqjeff |
| Posted: Tue Jul 16, 2013 4:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bruce2359 wrote: |
| muralihegde wrote: |
| Trying to avoid file system full scenario due to queues filling up on one queue manager causing damage to other queue managers.. |
Exactly what errors are you seeing? Which qmgr(s)? Exactly what is filling the filesystem? Are you certain it's an mq application? |
I think that muralihegde is planning ahead, and saying "this qmgr is not allowed to interfere with this other qmgr".
perfectly reasonable. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 16, 2013 5:00 am Post subject: Re: File System mount point change for existing queue manage |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| muralihegde wrote: |
There is a plan to create dedicated file systems for each of the queue managers and mount the directories for each of these queue managers on the individual file systems. |
So, the plan includes creating a separate volume group (or equivalent) for each qmgr?
| muralihegde wrote: |
| There is no change in the directory structure, but the underlying file system mount points are different and this change would involve mounting the existing folders on to new file systems. |
So, the plan does NOT include creating a separate volume group for each qmgr?
_________________
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 |
|
|
|
|
