| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to rebuild ConfigMgr without rebuilding brokers? |
« View previous topic :: View next topic » |
| Author |
Message
|
| panasci |
 Posted: Wed Apr 13, 2005 1:49 pm Post subject: How to rebuild ConfigMgr without rebuilding brokers? |
 |
|
Newbie
Joined: 19 Jun 2003
Posts: 4
Location: Port Hadlock, WA USA
|
Have a situation where the config mgr db is corrupt and it would be a problem to restore to last known good backup, so want to drop the db and recreate. Can't have broker (on AIX) offline for more than a few minutes, so broker rebuild is a last resort.
A coworker pointed me to a www.mail-archive.com thread discussing just this scenario. It says to stop the broker, then delete the broker UUID file at /var/mqsi/registry/<brokername>, then restart the broker. When the new ConfigMgr connects it passes a new UUID to the broker and the file is recreated. I suspect that a complete deploy at this point creates a whole new set of records in the broker db with the new UUID. The coworker has done this in the past and it worked.
I've been trolling for the past few hours and can't find anything discussing this process except this one email thread. Anybody done this or have any comments?
Env Info:
Win2k, WBI 5.0.1.4, DB2 8.1.5 (CM db is local)
Brokers on AIX 5.2, WBI 5.0.1.4, db2 8.1.6 (Broker db is local) |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Thu Apr 14, 2005 2:28 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Hi there,
The issue is how to get the Config Manager to recognise the existing deployed state of the broker including message flow assignments, subscriptions etc.
On 2.1, if you import your message flows etc. into the new CM database and reassign them the complete deploy will work, as the CM is able to recommunicate the entire state sent to the broker.
On v5, you will need to redeploy your BAR files in order to see the correct run state in the tooling. It's a bit more long winded (a side effect of making the message flow repository pluggable and moving it into the tooling) but at least this can be done one broker at a time.
In either version, existing subscriptions will not get reported back to the CM.
-Matt |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Apr 14, 2005 4:34 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
As a footnote, it's probably worthwhile getting IBM support to help you out here; restoring the CM database while keeping a broker going is not for the faint hearted 
Out of interest, how did the CM database get corrupt in the first place?
-Matt |
|
| Back to top |
|
|
| lillo |
| Posted: Thu Apr 14, 2005 6:37 am Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
Here are a step a found in MQSeries list recently. We tested and worked correctly.
| Quote: |
Backing Up:
* Stop the Broker.
* Run mqsiservice for the Broker and note the BrokerUUID value.
* Stop the ConfigMgr.
* Backup the ConfigMgr Database.
* Backup the Broker Database.
Restoring:
1. * Stop the Broker.
* Stop the ConfigMgr.
* Exit from the Brokers Toolkit/Control Center.
* Delete the Broker -w.
* Delete the ConfigMgr -w -n.
* Drop the Broker Database.
* Drop the ConfigMgr Database.
2. * Create the Broker Database.
* Create the ConfigMgr Database.
* Create the ConfigMgr.
* Create the Broker with the same name as the original.
* Start the ConfigMgr.
* Start the Broker.
* Run the Brokers Toolkit/Control Center.
* Connect to the ConfigMgr.
* Create the new Broker in the toolkit/Control Center.
* Deploy the topology.
3. * Stop the Broker.
* Stop the ConfigMgr.
* Restore the ConfigMgr Database.
* Restore the Broker Database.
* Run mqsiservice for the Broker using the -r option to set the BrokerUUID to the value noted during backup.
* Start the ConfigMgr.
* Start the Broker.
* Connect to the ConfigMgr.
* Deploy the topology.
|
Best regards,
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
| panasci |
| Posted: Thu Apr 14, 2005 7:36 am Post subject: |
|
|
Newbie
Joined: 19 Jun 2003
Posts: 4
Location: Port Hadlock, WA USA
|
Thanks for the feedback. I'm not sure how the CM db became corrupted. Either the backup used during the server rebuild was corrupt, which is unlikely but we're trying to determine that now, or db2 corrupted it. We have had some db2 issues due to an installation problem. The plan is to reinstall db2, which will probably lose the CM db, hence the planning for CM rebuild.
FYI, I opened a PMR and talked to support about the CM rebuild methodology my original post descrived. They said that other customers had reported doing this successfully, but others had problems and eventually had to recreate brokers. The environments experiencing problems were pretty complex. The support rep said that since rebuilding the CM this way was not problem-free, and they had not tested it exhaustively, they don't recommend it.
Seems like if the alternative is to recreate the brokers anyway, it's worth a shot. I'll be trying it, but we need to get db2 reinstalled and healthy first. |
|
| 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
|
|
|
|
