| Author |
Message
|
| sijtom0703 |
 Posted: Tue Oct 23, 2012 2:07 pm Post subject: Migrating Queue Manager from MQ v6.0 to v7.0 |
 |
|
Voyager
Joined: 28 May 2011
Posts: 84
Location: USA
|
Hi,
While migrating a Queue Manager from version 6.0 to version 7.0 of the Product to a new server box.
1. Is there any key point to be considered while copying data files of version 6.0 to version 7.0.
2. Is there any key point to be considered while moving ssl files [key store and certs] from v6.0 to v7.0.
please advice. |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Oct 23, 2012 2:18 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
It's all in the migration guide within the Info Centre.
_________________
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 |
|
|
| sijtom0703 |
| Posted: Tue Oct 23, 2012 2:40 pm Post subject: |
|
|
Voyager
Joined: 28 May 2011
Posts: 84
Location: USA
|
| I am talking specifically about RHEL server version? I couldn't find any in the Infocenter related to copying queue manager data files. The message data structure is different in both versions. But is that going to create any issues while migrating |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 23, 2012 4:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sijtom0703 wrote: |
| I couldn't find any in the Infocenter related to copying queue manager data files. |
Because you wouldn't want or need to.
| sijtom0703 wrote: |
| The message data structure is different in both versions. |
Not to an application it isn't. When you first start a queue manager after it's been migrated the logs and other internal structures are automatically reworked into the new structure. You don't copy anything.
| sijtom0703 wrote: |
| But is that going to create any issues while migrating |
It's going to create the issue indicated in the documentation; that if you want to revert to v6 you'll need to restore from a system level backup.
What do you think needs copying?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sijtom0703 |
| Posted: Sun Nov 04, 2012 1:00 pm Post subject: |
|
|
Voyager
Joined: 28 May 2011
Posts: 84
Location: USA
|
I don't know. I haven't figured out that yet
Is it that for MQv7.0.1 the file system needs to be POSIX compliant to take advantage of Multi-instance QM? It can't be .. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Nov 04, 2012 1:45 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| sijtom0703 wrote: |
I don't know. I haven't figured out that yet
Is it that for MQv7.0.1 the file system needs to be POSIX compliant to take advantage of Multi-instance QM? It can't be .. |
look, you don't do migration by creating a new piece of kit, installing mq, and then copying the qmgr files to the new machine.
You do migration by uninstalling previous levels (if at levels that do not allow coexistance) and then installing the new level on the *same* kit, and then starting up the queue manager.
OR you use dmpmqcfg/saveqmgr to dump an extract of the objects that exist on the "old" qmgr and then create a *new* qmgr at the new level, and then running the runmqsc created from dmpmqcfg on the new qmgr.
Never copy MQ internal files from one machine to another. |
|
| Back to top |
|
|
| sijtom0703 |
| Posted: Mon Nov 05, 2012 8:28 am Post subject: |
|
|
Voyager
Joined: 28 May 2011
Posts: 84
Location: USA
|
Thank you Jeff for clearing that out.
So as I understand when you uninstall MQ v6 the data and log files directories remain there untouched and when you install MQ v7 on the same location those data and log files goes into the new version and when Queue Manager restarted the old Queue Manager data and configuration are migrated to new ones.
I got the copy MQ internal files from one machine to another from the create backup queue manager from an existing queue manager steps in the info center. |
|
| Back to top |
|
|
|
|
