Author |
Message
|
dexter |
Posted: Thu Mar 10, 2011 8:11 am Post subject: Broker restart required as part of maintenance? |
|
|
 Apprentice
Joined: 07 Jan 2011 Posts: 32 Location: Michigan, USA
|
WMB v7, MQ v7, SUSE Linux v11
Four environments: DEV, SIT, QA and PROD.
One broker in each environment. One QM for each broker.
Typically, is a restart required for the broker as part of scheduled maintenance? Would the broker get sluggish or display erratic/erroneous behavior if not recycled for long durations of time?
I have daily broker backups set up. No multi-instance setup. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Thu Mar 10, 2011 8:22 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
In my experience, Broker can run for months at a time without a restart. We generally do not restart Broker unless we deploy new code. Then we restart to assure the classloaders are loading the new classes.
Backing up the filesystem won't help you all that much. You need to have an emergency rebuild plan in place that starts from ground zero with new hardware and stands up a system.
Issues with group and user numbering, among other problems, makes filesystem backups less valuable. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
dexter |
Posted: Thu Mar 10, 2011 8:26 am Post subject: |
|
|
 Apprentice
Joined: 07 Jan 2011 Posts: 32 Location: Michigan, USA
|
Thanks LanceLot.
As a matter of fact, I do have a broker environment setup script that builds all the WMB/MQ components from scratch and sets up connectivity with the data sources.
I was of the same opinion (no restart required). I just wanted a second opinion from the experts. So, thanks again. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Thu Mar 10, 2011 8:31 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
You are most welcome.
I would go further with your script: You need human readable step-by-step instructions and all associated binary resources (executables, BAR files, Jar files) to start with a brand new system and stand up your production environment from scratch. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
dexter |
Posted: Thu Mar 10, 2011 8:48 am Post subject: |
|
|
 Apprentice
Joined: 07 Jan 2011 Posts: 32 Location: Michigan, USA
|
Well, my job starts after the unix admin installs the product.
But human readable instructions are part of the script. |
|
Back to top |
|
 |
dexter |
Posted: Thu Mar 10, 2011 8:52 am Post subject: |
|
|
 Apprentice
Joined: 07 Jan 2011 Posts: 32 Location: Michigan, USA
|
And yes, we have automated our build/deploy process too. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Thu Mar 10, 2011 8:56 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
If your lone production server became engulfed in flames (God forbid), and your CTO came to you, asking you this question: "dexter, how long before we can resume business?" what would your answer be? _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Mar 10, 2011 9:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It rather depends on which file system you are backing up, and under what conditions, as to whether or not it is actually useful to do so.
In v7, for example, one would merely run mqsibackupbroker and then backup the output archive files.
One would also examine and review the documentation on said command to determine the conditions that are necessary to create a reliable backup. And then determine the necessary frequency to meet business contingency guidelines.
Being able to rebuild a broker at the last good point in time through other means is a valuable tool. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Thu Mar 10, 2011 9:30 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
mqjeff wrote: |
It rather depends on which file system you are backing up, and under what conditions, as to whether or not it is actually useful to do so.
In v7, for example, one would merely run mqsibackupbroker and then backup the output archive files.
One would also examine and review the documentation on said command to determine the conditions that are necessary to create a reliable backup. And then determine the necessary frequency to meet business contingency guidelines.
Being able to rebuild a broker at the last good point in time through other means is a valuable tool. |
The Info center has this:
Quote: |
You can restore a broker only on a computer that has an identical configuration; the operating system must be at the same level, and the broker and queue manager names must be identical. |
Not always is it convenient or possible to have the OS at the same level between two systems that were built several years apart. That is why I prefer the ability to quickly standup a system from scratch. That way, your not stuck trying to find that OS patch that somehow is not online for download anymore. You just run with the latest and greatest OS, WMB/MQ rpm's, BARs&Jars, etc. Guaranteed operational in the shortest amount of time. Of course, regular exercising of these human readable step-by-step instructions are required to ferret out any oversight; especially those that creep in from the passage of time and OS levels. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Mar 10, 2011 11:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
lancelotlinc wrote: |
Not always is it convenient or possible to have the OS at the same level between two systems that were built several years apart |
I nearly think I agree with you
mqjeff wrote: |
Being able to rebuild a broker at the last good point in time through other means is a valuable tool. |
 |
|
Back to top |
|
 |
|