| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Restore broker without having ConfigMgr database |
« View previous topic :: View next topic » |
| Author |
Message
|
| the_one |
 Posted: Mon Aug 10, 2009 10:51 pm Post subject: Restore broker without having ConfigMgr database |
 |
|
Novice
Joined: 16 Dec 2008
Posts: 22
Location: PHX, AZ
|
Hi All,
I m trying to clone a broker domain from TSM backup files. Here are product details:
BRK1 - (Broker v 6.0) AIX
QM1 - ( MQ v6.0) AIX
BRKDB01 - (db2 v9.1) AIX
QMC1 - ConfigMgr Windows
I finally got the broker up and running fine on a TEST AIX server. But couldn;t get the broker topology via ConfigMgr.
The only missing piece in this jigsaw is the ConfigMgr Database. We are not able to get the restore for the Windows machine as per our current backup policies.
I wanted to know that, is there a way we can sync the two databases? Or something else that needs to be done which can aid in restore
TA |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Aug 11, 2009 6:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you were using 6.1, you could create an entirely new ConfigMgr and adopt the Broker.
It's not clear how you can say that you have restored the ConfigMgr in any meaningful way, nor cloned the broker domain, without a backup of the ConfigMgr repository.
So either someone has asked you to do something impossible, or you have failed to communicate the requirements of what they have asked properly to the team managing the backup policies.
On the third hand, it might be easiest to just use MQSC scripts and BAR files to create an entirely NEW broker and NEW configMgr that has the SAME topology and SAME deployed flows and sets as the existing one.
It might even produce a faster restore time. |
|
| Back to top |
|
|
| the_one |
| Posted: Tue Aug 11, 2009 3:46 pm Post subject: |
|
|
Novice
Joined: 16 Dec 2008
Posts: 22
Location: PHX, AZ
|
| mqjeff wrote: |
| It might even produce a faster restore time. |
Thanks Jeff and I understand that building a fresh server takes lesser time and is a clean approach as well.
But as you might have understood this already is that, this is part of DR exercise and we have to make this DR independent of our code repository. (i.e. MQSC and flows wont be availble at DR site)
| mqjeff wrote: |
| It's not clear how you can say that you have restored the ConfigMgr in any meaningful way........... |
I sent a couple of test messages thru the broker and its processing them fine, except the fact that I am not able to make changes to the topology.
| mqjeff wrote: |
| If you were using 6.1, you could create an entirely new ConfigMgr and adopt the Broker. |
So does that confirms that with this version of broker, we cant assign it to new configMgr?
I can create a script, that can take the backup of the ConfigMgr and store it so that it can be later backed up, but the problme is that backupconfigmgr command cannot work with component runnnig 
I still hope there might be some way around for that. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Aug 11, 2009 5:43 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| the_one wrote: |
But as you might have understood this already is that, this is part of DR exercise and we have to make this DR independent of our code repository. (i.e. MQSC and flows wont be availble at DR site)
|
They better be. Or does your business never plan to make a Message Flow change after a DR?
| the_one wrote: |
| mqjeff wrote: |
| It's not clear how you can say that you have restored the ConfigMgr in any meaningful way........... |
I sent a couple of test messages thru the broker and its processing them fine, except the fact that I am not able to make changes to the topology.
|
"...thru the broker..." You restored the runtime environment, but not the Config Manager needed to manage that environment, as Jeff said.
| the_one wrote: |
| mqjeff wrote: |
| If you were using 6.1, you could create an entirely new ConfigMgr and adopt the Broker. |
So does that confirms that with this version of broker, we cant assign it to new configMgr?
|
That's right. A HUGE reason to upgrade to 6.1.0.4. Start planning now. 
| the_one wrote: |
I can create a script, that can take the backup of the ConfigMgr and store it so that it can be later backed up, but the problme is that backupconfigmgr command cannot work with component runnnig
|
You are deploying code to production constantly, 24x7? Take your Config Manager down once or twice a day, for 5 minutes, back it up and restart it. The developers and deployers will know when your Production Config Manager is down every day for its backup and will somehow manage.
Or have a seperate DR Config Manager with a seperate DR Broker, deploy to your DR WMB components anytime you deploy to Production, and avoid the issue altogether.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| the_one |
| Posted: Tue Sep 08, 2009 4:34 pm Post subject: Thanks!!! |
|
|
Novice
Joined: 16 Dec 2008
Posts: 22
Location: PHX, AZ
|
| PeterPotkay wrote: |
That's right. A HUGE reason to upgrade to 6.1.0.4. Start planning now.
|
Thanks Peter.
The point is well taken and I have already started working over the broker upgrade.
For this DR (just for this one), I will be restoring just the runtime and since we are not expecting any changes to the domain, we are good without any config manager server.
Also, as mentioned in my previous posts, our configmanagers are hosted on seperate windows machines so I will be working over to move those to AIX as well. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 09, 2009 5:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Here's the thing.
If you restore JUST the broker, as a means of accomplishing DISASTER RECOVERY, then yes. You have, to some extent, recovered from disaster.
You are now back up and running. In a crippled sense, in that you can not apply any configuration changes at all.
In order to give you the ability to apply any configuration changes, you have to completely rebuild the environment that you've just restored.
So you've recovered from disaster, but left yourself with another full rebuild effort in your near future.
Remember that one of the main premises of proper DR planning is that the original environment has been destroyed down to the last atom by the unwarranted wrath of the diety of your choice. |
|
| Back to top |
|
|
| the_one |
| Posted: Thu Sep 10, 2009 10:21 am Post subject: |
|
|
Novice
Joined: 16 Dec 2008
Posts: 22
Location: PHX, AZ
|
| mqjeff wrote: |
| Remember that one of the main premises of proper DR planning is that the original environment has been destroyed down to the last atom by the unwarranted wrath of the diety of your choice. |
I agree  . And btw nice-scary selection of words too
I went thru the steps for Migrating to 6.1 from 6.0 and seems like we will have to build all servers fresh (recompiling/redeploying flows with new eqsl version). This seems HUGE. |
|
| 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
|
|
|
|
