| Author |
Message
|
| exerk |
 Posted: Tue Mar 15, 2011 11:51 pm Post subject: |
 |
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| PeterPotkay wrote: |
| exerk wrote: |
| The only way to take a proper back-up, be it logs and/or file system, is to stop anything using the queue manager (and that included message channel agents) and end the queue manager. |
I don't know if that statement is entirely true when dealing with Back Up QMs.
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqzag.doc/fa14740_.htm
| Quote: |
To ensure that a backup queue manager remains an effective method for disaster recovery it must be updated regularly. Regular updating lessens the discrepancy between the backup queue manager log, and the current queue manager log. There is no need to stop the queue manager to be backed up.
|
|
Note my "...and/or file system..." qualification 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Mar 16, 2011 3:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| exerk wrote: |
| PeterPotkay wrote: |
| exerk wrote: |
| The only way to take a proper back-up, be it logs and/or file system, is to stop anything using the queue manager (and that included message channel agents) and end the queue manager. |
I don't know if that statement is entirely true when dealing with Back Up QMs.
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqzag.doc/fa14740_.htm
| Quote: |
To ensure that a backup queue manager remains an effective method for disaster recovery it must be updated regularly. Regular updating lessens the discrepancy between the backup queue manager log, and the current queue manager log. There is no need to stop the queue manager to be backed up.
|
|
Note my "...and/or file system..." qualification |
I'm not sure I follow your distinction.
There is a difference between taking a backup of a queue manager - which only makes sense to do when the qmgr is stopped - and using a backup qmgr.
I'm not otherwise sure where whskibum is in this thread... have you been answered? |
|
| Back to top |
|
|
| wskibum |
| Posted: Wed Mar 16, 2011 4:58 am Post subject: |
|
|
Apprentice
Joined: 03 Jul 2008
Posts: 38
Location: Northern California
|
| Yes, thank you. I have gotten some very good information from this thread. |
|
| Back to top |
|
|
| wskibum |
| Posted: Wed Mar 16, 2011 3:15 pm Post subject: |
|
|
Apprentice
Joined: 03 Jul 2008
Posts: 38
Location: Northern California
|
Ugh. It's not working. I am using scp to move the log to the backup qmgr, and I can read the log in. When I try and activate the log I get:
AMQ7017: Log not available.
So it seems either I need to ship more than just the log, or I need to use another method of shipping the file so all the bits are shipped together.
Any ideas? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Mar 16, 2011 3:41 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| wskibum wrote: |
I am using scp to move the log
.
.
.
So it seems either I need to ship more than just the log |
You used the word "log", singular.
The instructions here:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqzag.doc/fa14740_.htm
make it sound like you need to move more than just one file anytime you update the back up QM.
I have zero experience with this, so I may be completely off base.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Mar 17, 2011 12:10 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| wskibum wrote: |
| So it seems either I need to ship more than just the log, or I need to use another method of shipping the file so all the bits are shipped together. |
Did you do the initial step of taking copies of all the existing queue manager’s data and log file directories (including all subdirectories), and then overwrite the backup queue manager's data and log file directories with those copies?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| wskibum |
| Posted: Thu Mar 17, 2011 8:22 am Post subject: |
|
|
Apprentice
Joined: 03 Jul 2008
Posts: 38
Location: Northern California
|
Yes. I shut down the production qmgr and tarred up data and log directories, then over wrote the backup qmgr files.
Interesting, I read in a few more log files and the issue went away. So it's like there is something in the actually extent log files that is required but may be missing from some of the logs I am shipping. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Mar 17, 2011 10:46 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| wskibum wrote: |
| ...I read in a few more log files and the issue went away. So it's like there is something in the actually extent log files that is required but may be missing from some of the logs I am shipping. |
Hence my advice in regard to ensuring point-in-time consistency by ending a queue manager, even though the manuals say it isn't necessary just for 'shipping' logs.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| wskibum |
| Posted: Thu Mar 17, 2011 10:53 am Post subject: |
|
|
Apprentice
Joined: 03 Jul 2008
Posts: 38
Location: Northern California
|
| In the lab, I had the same problem happen last night with 1 of the tarred backups taken after the qmgr had been shut down. Very strange. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Mar 17, 2011 12:36 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Exerk, the manuals explicitly state a QM does not need to be shut down to get the data over to the Back Up QM server to keep it up to date*. The solution would be useless if you had to stop the primary QM every time you wanted to sync up the Back Up QM.
If you DO have to stop the QM, then its a product flaw and a PMR should be opened.
* Not talking about the initial "load" of the Back Up QM, where they do tell you to back up the original QM in a classic fashion, i.e. stop it first. But that is not the problem that wskibum is having if I understand him correctly. He is (was) having problems updating it.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Mar 17, 2011 1:49 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| PeterPotkay wrote: |
Exerk, the manuals explicitly state a QM does not need to be shut down to get the data over to the Back Up QM server to keep it up to date*. The solution would be useless if you had to stop the primary QM every time you wanted to sync up the Back Up QM.
If you DO have to stop the QM, then its a product flaw and a PMR should be opened.
* Not talking about the initial "load" of the Back Up QM, where they do tell you to back up the original QM in a classic fashion, i.e. stop it first. But that is not the problem that wskibum is having if I understand him correctly. He is (was) having problems updating it. |
In full agreement with both you and the manuals, but it's not something I'd want to hang my hat on, and that's why I'm neither a fan of, nor recommend back-up queue managers; rapid rebuild is my preference.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 17, 2011 8:36 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
I am not a fan of the "backup qmgr" myself, however I can see where it could be interesting when your systems require a point in time recovery vs a recovery to the last failure point... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wskibum |
| Posted: Sat Mar 19, 2011 8:48 pm Post subject: |
|
|
Apprentice
Joined: 03 Jul 2008
Posts: 38
Location: Northern California
|
So, I am doing everything by the book and you guy's think MQ is broken?
I will contact IBM support and see what can be done.
Thank you all for your help! |
|
| Back to top |
|
|
| wskibum |
| Posted: Wed May 04, 2011 1:18 am Post subject: |
|
|
Apprentice
Joined: 03 Jul 2008
Posts: 38
Location: Northern California
|
Just to let everyone know the outcome of all this. I contacted IBM support and after considerable wrangling /finger pointing, etc determined that this was a bug in the code. To be specific in one of the lib files.
lib/libmqml_r.so LIBRARY
lib64/libmqml_r.so LIBRARY
They identified the code causing the problem quickly and issued a fix.
I assume this will be added to the next Linux release.
### README Provided by IBM
Fix name: 7.0.1.3-WS-MQ-LinuxX64-TFP26657
Build number: 38628
Product: WebSphere MQ V7.0.1 (WS-MQ)
Platform: Linux x86-64 platform (LinuxX64)
Maintenance level: 7.0.1.3 *** ONLY APPLY THIS FIX TO A 7.0.1.3 |
|
| Back to top |
|
|
|
|
