| Author |
Message
|
| sjensen |
 Posted: Sun Apr 17, 2005 9:51 am Post subject: Migrating Broker and NEON DB to new Machine |
 |
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
We are going to migrate our broker to a new machine and we also use Neon.
The Broker is currenly WMQI 2.1 CSD7 on Solaris 8 with WMQ 5.3 CSD 5 usinf Oracle 8 and will be moved to a Solaris 8 machine with WMQI 2.1 CSD 7 and WMQ 5.3 CSD 8. The config manager is on Widows NT and will not be migrated.
My understanding of the steps to migrate the broker are:
Export everything from Config Manager for safety.
Delete Broker in Config Manager
Deploy
Check logs to verify deploy went OK.
Delete Broker on Unix
Create Breoker on Unix
Create Broker on Config Manager
Deploy all
Is it neccessary to delete all flows from the broker and deploy an empty Broker from the Config Manager first before deleting it?
With respect to NEON the DBAs want to migrate to a database with a new name. Is it possible if we keep all the data to simply change the nnsyreg.dat file to point to the new database or do we need to import all the NEON rules etc? Can we even avoid running inst_db or do we have to recreate the NEON database from scratch?
Many thanks
Stefan |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Mon Apr 18, 2005 1:59 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Hi Stefan,
The first deploy is not necessary if you're using a different name and queue manager for the broker; because it's in effect a completely different broker. The delete can be done after you've created and deployed the new broker.
If you want to reuse the same broker name you do need to do the first deploy, so that the Config Manager can tidy up the association between the broker's name and the first machine.
That deploy also allows the broker to cleanly tidy up its resources before the component is deleted.
In either case, you don't need to individually delete your message flows, as the delete of the broker reference from the Control Center will handle all that for you.
The key point is, after removing a broker reference always ensure that the topology deploy is successful before deleting the broker component. (Hope that makes sense!) Otherwise, the Config Manager won't be able to tidy up the references to the old broker (because it can't verify that the broker has successfully gone away).
Sorry, I'm not enough of a New Era expert to help with your second question 
HTH
-Matt |
|
| Back to top |
|
|
| sjensen |
| Posted: Mon Apr 18, 2005 3:31 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Thanks Matt.
Unfortunately we have to keep the Broker name so I do need to do the initial delete/deploy.
One more question. I do not know a way to save the execution groups. Is the only way to save the definitions of them on paper and then recreate all the EGs?
Many thanks
Stefan |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Apr 18, 2005 3:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You might be able to follow the procedures to recover a database from backup as a way to move the broker to a new machine with the same name and the same UUID.
Then you wouldn't have to delete and recreate it in the ConfigMgr, and also not lose your EGs.
The System Administration guide for 2.1 has a good description of how to backup and restore a broker.
It's a real shame that the 5.0 documentation DOESN'T.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Apr 18, 2005 3:56 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| sjensen wrote: |
Is the only way to save the definitions of them on paper and then recreate all the EGs?
|
There is no easy way of recreating execution groups - at the moment. 
The best approach is to note the execution groups down on paper and recreate them in the tooling - also the least technical approach.
Alternative solutions would involve hacking XML data in the Config database, which I certainly wouldn't recommend.
-Matt |
|
| Back to top |
|
|
|
|
