Kulbir,
You didn't say
what platform you're doing this on. I do just mainframes, but expect you'd have
the same problems on smaller ones.
If you don't
replicate the log files and you have any persistent messages on your queues when
you go through your exercise below, then you'll have problems. MQ needs the log
files then. If you get out of sync, you'll never be able to bring up your queue
manager.
Ò¿Ó
Bob Juch
Citigroup
MQ Mainframe Support
Team
Weehawken, NJ
201-974-2147
mailto:[EMAIL PROTECTED]
-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Kulbir S. Thind
Sent: Wednesday, November 17, 2004 12:05 PM
To: [EMAIL PROTECTED]
Subject: Backing up "Q" files but not the "LOG" files
Hi,
We're thinking about setting up replication for our queue manager to ensure that just the Q files are backed up but not the LOG files for the queue manager. This is being contemplated as it appears the log files are updated far more than the Q files as the LOG files are doing internal MQSeries checks, etc. We need to reduce the amount of data that we're replicating.
My first thoughts on this were that this would not work as the Q files would be out of sync with the LOG files. However we performed the following:
- Created a queue manager
- Started the queue manager
- Created some queues
- Put some message on the queues
- Ended the queue manager
- Took a copy of the LOG files used by the queue manager
- Started the queue manager
- Put some more messages on the queues
- Created another queue object
- Ended the queue manager
- Restored the LOG files that were backed up in step 6
- Started the queue manager
At this point I was expecting issues but I found that the queue manager started without problems and it recognised the queue that was created in step 9. Does this mean if we took a copy of the LOG files and restored them to a queue manager at a later point retaining the latest Q files we would have no problems? Has anyone tried this or no of any problems?
Cheers,
Kulbir.
