| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Backup/recovery - AMQ7017: Log not available. |
« View previous topic :: View next topic » |
| Author |
Message
|
| vmcgloin |
 Posted: Wed May 15, 2002 4:26 am Post subject: Backup/recovery - AMQ7017: Log not available. |
 |
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
I get "AMQ7017: Log not available." when running strmqm, after recovering the queue manager from system backups. (MQ5.2 on AIX)
Logging is circular.
I know I can copy the logs from a new queue manager to enable the failed one to start, but then I lose any persistent messages I had on the queues which is unacceptable.
Steps I took:
1. endmqm
2. archive recent logs: /var/mqm/log/QMNAME/ and /var/mqm/qmgrs/QMNAME/@ipcc/AMQRSYNA.DAT
3. Restore the qmgr files from system backup: /var/mqm/qmgrs/QMNAME and /var/mqm/log/QMNAME
4. Restore the newest logs and AMQRSYNA.DAT
5. Restart the queue manager
Any ideas?
Thanks, Vicky |
|
| Back to top |
|
 |
| jhalstead |
| Posted: Wed May 15, 2002 8:38 am Post subject: |
|
|
Master
Joined: 16 Aug 2001
Posts: 258
Location: London
|
I've never really had any problems retaining persistent messages when replacing the log files, the persistent messages are in the queue files so they should be okay. Any operations that were not commited when the queue manager failed will be lost though.
You are right to be cagey though, I'd back up all the queue files before trying to replace the logs. I'd create the new queue manager with the same name & qmgr attributes (different AIX box) and replace the logs and log control file. Leave the queue files as they are.
When you bring the queue manager up the old queue should be their with it's messages.
If this doesn't work (not happened to me) then you can always replace the relevant queue files from your backup.
I know this is a bit of a hack, however it's got to be worth a try. Good luck.
Jamie |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed May 15, 2002 11:59 pm Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
| jhalstead wrote: |
| the persistent messages are in the queue files so they should be okay |
Doh! Thank you! I did not know that. I was thinking that this information could be retrieved from the log files, but the error obviously refers to other logs in the queue directory.
To explain, I was testing recovery after corrupting the queues concerned by renaming (deleting) the /var/mqm/qmgrs/MyQmgr/queues/MyQueue folder, so when I recovered I had an old version of these files and I guess the qmgr was looking for the newer ones.
Thanks,
Vicky |
|
| Back to top |
|
|
| jhalstead |
| Posted: Thu May 16, 2002 7:27 am Post subject: |
|
|
Master
Joined: 16 Aug 2001
Posts: 258
Location: London
|
Vicky, hope all is well up in Scotland, apparently Kylie Minogue is up there at the moment - give her my best!
Ok. So I guess at the end of the day you want to recover messages when queue files get corrupted or deleted by a malicious system adminstrator...
If this is the case you're going to have to use linear logging and take media images before you backup. When using circular logging you can recover from corrupted log files, but not from corrupted queue files.
Linear logging has the additional disk space & administrative overhead, however it is the only real way to get MQs assured delivery. Support pack MS62 has a perl script to remove/compress logs no longer required for queue manager start up or media recovery.
J |
|
| 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
|
|
|
|
