|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Move QM to another Machine |
« View previous topic :: View next topic » |
Author |
Message
|
Caket |
Posted: Mon Nov 18, 2013 12:41 am Post subject: Move QM to another Machine |
|
|
Novice
Joined: 07 Aug 2010 Posts: 10
|
MQ 70, windows server.
I have done some testing of moving queue managers between machines, this is moving and not recreating.
So important MQ data (files,reg) are copied to the new machine and then started. This comes up fine and the restored broker also processes messages.
I have not seen any doc where this is supported process.
I am confident this will not create problems and it has been months since it was done.
I did this as some else said they did this a few times with unix systems. I would like to ask if there anyone has any info, whether that be IBM or personally where doing this type of work is documented or defined as an approved/accepted method of moving QM's between machines. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 18, 2013 6:04 am Post subject: Re: Move QM to another Machine |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Caket wrote: |
I have not seen any doc where this is supported process. |
It's not.
Caket wrote: |
I am confident this will not create problems |
Good for you. Confidence is important.
Caket wrote: |
I would like to ask if there anyone has any info, whether that be IBM or personally where doing this type of work is documented or defined as an approved/accepted method of moving QM's between machines. |
It's not an approved, accepted or supported means of moving a queue manager. IBM provide a number of tools by which the configuration of a queue manager can be unloaded & reloaded into a newly created queue manager on the new target box (saveqmgr and it's in-product replacement). You can probably get any number of endorsements from people here who've done something similar and not encountered problems. This doesn't make it supported, not will it help with your managerment if you encounter problems - "well a bunch of random, anonymous & unaccountable strangers on the Internet said it was fine" tends not to be a great conversational opening!
Speaking personally I'd be more confident of this method on a unix box (where the configuration is in files) than on Windows (where it's in that dark pit called the registry). In any event, I beleive the time you save doing this as opposed to unloading / reloading the queue manager (or better still building the queue manager from the original scripts you have in your change control system) does not justify the risk of the method. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|