| Author |
Message
|
| solomita |
 Posted: Wed Aug 04, 2004 7:04 am Post subject: Backup & Recovery |
 |
|
Voyager
Joined: 06 May 2003
Posts: 94
|
The client is currently running V2.1 and their backup/recovery procedure is as follows:
Backup
Stop ConfigMgr
Stop applications connected to WMQI databases
Backup ConfigMgr and MRM databases (they dont back up broker ones)
Re-start Config Mgr
Recovery
Rebuild ConfigMgr Server
Restore ConfigrMgr and MQM databases
Create ConfigMgr
Rebuild Broker Server
Create Brokers
Build/Connect MQ Channels
Start brokers/Config Mgr
In the Control Center, A Complete Configuration is done to ensure consistency across the broker domain
This has been tested and works for them. The question is can this same process be done in V5 so I gave it a shot. This is what I did locally on my machine:
Backed up ConfigMgr database
Deleted Broker(with -w option)/ConfigMgr (with -w -n option)
Deleted Broker/ConfigMgr databases
Recreated Broker/ConfigMgr databases
Restored ConfigMgr database
Recreated Broker/ConfigMgr
Connected MQ Channels
Started Broker/ConfigMgr
In the toolkit, connected to the Config Mgr and the Topology contained the broker and egs and bar files. However, I was not able to deploy without errors.
So basically, I did the same steps that were done in V2.1 but it does not work the same. The client is trying to avoid unnecessary backup steps (ie backing up broker databases/tables) as they have done in V2.1 but it appears that short of removing deployed children and re-adding bar files to the eg's, they will have to back up the dbase.
Anyone have other suggestions on how to do this or can confirm that the broker dbase tables definitely need to be backed up even though they didnt have to be in V2.1? |
|
| Back to top |
|
 |
| wooda |
| Posted: Wed Aug 04, 2004 8:47 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
Hi,
| Quote: |
| In the toolkit, connected to the Config Mgr and the Topology contained the broker and egs and bar files. However, I was not able to deploy without errors. |
Q1. Did you do a "Deploy Topology Configuration - > Complete" ? If not what did you do ?
Q2. What errors did you get when deploying? |
|
| Back to top |
|
|
| solomita |
| Posted: Wed Aug 04, 2004 8:53 am Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
Q1 - Yes I did a deploy topology -> Complete
I know the way to fix it is to either restore the broker db or remove deployed children and re-add them to the EG but we are trying to avoid those extra steps in a real scenario.
Q2:
BIP2062E: Broker WBRKBKDB (UUID 83449d26-fe00-0000-0080-af9e14a04725) Execution Group 'default' (UUID 84449d26-fe00-0000-0080-af9e14a04725) detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configuration. This could occur for any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit to redeploy to the Execution Group. Contact your IBM support center if you are unable to resolve the problem.
BIP2062E: Broker WBRKBKDB (UUID 83449d26-fe00-0000-0080-af9e14a04725) Execution Group 'default' (UUID 84449d26-fe00-0000-0080-af9e14a04725) detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configuration. This could occur for any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit to redeploy to the Execution Group. Contact your IBM support center if you are unable to resolve the problem.
BIP2062E: Broker WBRKBKDB (UUID 83449d26-fe00-0000-0080-af9e14a04725) Execution Group 'default' (UUID 84449d26-fe00-0000-0080-af9e14a04725) detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configuration. This could occur for any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit to redeploy to the Execution Group. Contact your IBM support center if you are unable to resolve the problem.
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| wooda |
| Posted: Thu Aug 05, 2004 3:59 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
Hi,
I think this is because in 2.1 a complete deploy used to delete and recreate the execution group. (So if it didn't exist it got created).
In V5 the complete topology doesn't recreate the eg.
Some interesting facts ...
"Deploy Topology Configuration - > Complete" Does not delete/recreate the execution group.
"Remove Deployed Children" Does delete/recreate the eg but if a successful response is received also removes the flows/sets from the eg in the configmgr. (which means in your case you have to drop the bar files again)
Dropping a bar on a newly created eg causes it to be created in the broker.
Dropping a bar on an eg with flows/sets already deployed does not cause it to be created in the broker.
If a response is not received from the broker the configmgr will not let you do any kind of deploy again unless you use "Cancel Deployment", when the configmgr will pretend it never did the deploy in the first place. |
|
| Back to top |
|
|
| solomita |
| Posted: Thu Aug 05, 2004 4:47 am Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
Thanks for the info....
So are you saying it cant/wont work the same in V5? Is there a way to delete/re-create the execution group without removing the message flows/sets (bar file)? The errors I received above are from the initial deploy after recreating the config mgr and broker and restoring the confi mgr database.
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| wooda |
| Posted: Thu Aug 05, 2004 5:18 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
Sorry as far as I know in V5 there is currently no legitimate way of delete/recreating the eg without removing the sets/flows held against that eg in the configmgr.
I suggest you raise a requirement on IBM for this as it seems a desirable function to have.
However what you could do is make use of the command line deploy utility "mqsideploy" to script the redeploying of the bar files to a new execution group after "remove deployed children".
This at least would result in fewer steps and allow the redeploy to be pre-prepared. (maybe at the same time as the backup takes place) |
|
| Back to top |
|
|
|
|
