| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Recreating MQSI 2.1 control center |
« View previous topic :: View next topic » |
| Author |
Message
|
| mrlazy |
 Posted: Wed May 03, 2006 4:54 pm Post subject: |
 |
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Sorry for nagging you guys with my questions, but I just want to take you experts advice before I take any major step(Since this is a production machine which I have to restore, I'm just more worried)
So what I understand from your replies, this is what I have to do(kindly correct this already confused fellow if wrong):
I MUST take DB2 backup from production (since I will not recreating brokers)
Restore it in the new machine after DB2 is freshly installed.
Then just go ahead and create config manager using the above data source,
I hope this doesn't need cause any issues the production in anyway!!
THANKS A LOT FOR YOUR REPLIES...
 |
|
| Back to top |
|
 |
| MikeC |
| Posted: Thu May 04, 2006 8:12 am Post subject: |
|
|
Acolyte
Joined: 30 Jun 2003
Posts: 55
Location: Toronto, Canada
|
I'm not sure that will work. The UUID is held as a registry setting in the broker. On the Config Mgr side, I don't think it's stored in the Configuration Database. .. If you want to avoid having to delete and re-create the broker, remove the broker from the topology and re-deploy. Now you're telling the broker that it isn't administered by this configuration manager anymore. .. Then you can create a new Config Mgr (on your new machine), add the original broker to your topology and deploy to it.
I believe that's the recommended way to switch Config Mgrs. Not backing up and restoring the database. .. But check the documentation to be sure.
_________________
-Mike. |
|
| Back to top |
|
|
| sirsi |
| Posted: Thu May 04, 2006 8:23 am Post subject: |
|
|
Disciple
Joined: 11 Mar 2005
Posts: 177
|
MikeC wrote:
| Quote: |
| On the Config Mgr side, I don't think it's stored in the Configuration Database. .. |
think it should be there in the ConfigMgr side otherwise how will it identify the broker...
mrlazy: you should create ConfigMgr first and then overlay the backup
take configDb and MessageReprository backup
create configmgr on new machine
overlay the config database backup.
So if you open ur control center u should see the broker already added
Am i right? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu May 04, 2006 8:44 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Fine.
I will go read the manuals again, and I will go search through here for the last time this was discussed, and I will post the right answer.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu May 04, 2006 8:44 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Fine.
I will go read the manuals again, and I will go search through here for the last time this was discussed, and I will post the right answer.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mrlazy |
| Posted: Thu May 04, 2006 8:45 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Now it's more confusing for an already confused fellow like me!!!
All I'm looking is when I deploy the imported/exported msg flows/sets from production to the new control center,It should work fine.
It doesn't mmatter whether the topology is already in there or I create a topology simlar to production, but since the brokers are located on AIX(which will be restored), they should be registered with newly created config mgr (in new machine).
Did I make my point clear? If not, I can do it in a detailed way.. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu May 04, 2006 8:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You don't deploy FROM production TO control center. Deployment always goes FROM control center TO ConfigMgr And then TO Production.
http://www.mqseries.net/phpBB2/viewtopic.php?t=20267&start=0&postdays=0&postorder=asc&highlight=
| http://publibfp.boulder.ibm.com/epubs/pdf/bipyag05.pdf wrote: |
Configuration Manager
If the Configuration Manager environment is damaged, or one or more of the
database tables are corrupted, you must perform the following sequence of
operations to recover it:
Step 1. Ensure that all Control Center sessions are stopped.
Step 2. Stop the Configuration Manager using the mqsistop command.
Step 3. Stop the Configuration Manager’s queue manager using the endmqm
command.
Step 4. Delete the Configuration Manager using the mqsideleteconfigmgr
command or the Command Assistant:
a. If you are recovering the Configuration Manager because one or more
of the configuration repository or message repository tables is
damaged, you must delete these tables when you delete the
Configuration Manager, thus destroying all information pertinent to
the broker domain (not just data internal to the Configuration
Manager) . Therefore you must export everything you can from the
domain before you issue the mqsideleteconfigmgr command
specifying the flags -n -m.
b. If the database tables are undamaged, you must omit the flags -n -m.
This preserves your configuration data in both repositories.
Step 5. If you are recovering the Configuration Manager because one or more of
the configuration repository or message repository tables is damaged, you
must restore both repositories from a previously successful backup
version. (The data in the two repositories is interdependent, and you must
restore the entire contents of both. You cannot restore individual tables.)
Step 6. Recreate the Configuration Manager using the mqsicreateconfigmgr
command or the Command Assistant.
Step 7. Start the Configuration Manager using the mqsistart command.
Step 8. Start the Control Center, and select the Topology view.
Step 9. If you have completed Step 4a and Step 5, you must also redeploy the
domain configuration by selecting File —> Deploy —> Complete
configuration (all types) —> Normal to ensure that the configuration across
the broker domain is consistent. |
To sum up: If you are not moving the configmgr or the brokers, you don't need to back up the databases at all.
If you are moving the configmgr, and you are NOT moving the configmgr DB, then you can just mqsideleteconfigmgr (making sure you preserve data), move the Queue Manager (changing channels as needed) and then run mqsicreateconfigmgr on the new machine with the same DB.
If you are moving the ConfigMgr AND the configmgr DB, then you need to backup the configmgr DB, restore it to the new location and then run mqsicreateconfigmgr again pointing to the new (recovered) database.
None of these require you to change your brokers at all, this is why you backup and restore the configmgr database.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mrlazy |
| Posted: Thu May 04, 2006 9:11 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
THANKS FOR THE REPLY Jeff.
I didn't mean to say that the data is deployed to control center.
Since it just like creating a parallel environment, I will go ahead and backup & restore the DB2 to the new machine. Run saveqmgr script to save object def's and then import it to new machine.
Finaly create configmgr. Then deploy the imported msg flows/sets to the new config mgr.
Thanks a lot once again for your patience... |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
