I gueess it would all come down to your Business description of DR.
For some companies the are glad to be back up. In other cases they want to be back up as near to, if not exactly, like production when they went down. This is where a replication of the Logs and Queue Data directories are required. Just backing up the OBJECTS, which BTW isn't the only thing you need to do, is just going to give you back your QMGR. But without the state of data when it went down what good does that do your business. This is where the SLA requirements by them are very important. It transcribes down to $$$$$$$$$$$$ for them. "you want a car with all the options....get out the checkbook". These requirements are "SOMETIMES" give anbd take depending on the business requirements and hand in hand with the size of the pocketbook.
bobbee
From: Christopher Warneke <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Backing up "Q" files but not the "LOG" files Date: Wed, 17 Nov 2004 12:26:08 -0800
What I don't understand here, is the purpose of the replication. Are we trying to retain backups of the qmgr's objects, or both the objects and the messages?
If you are only trying to retain copies of the objects...
http://www-306.ibm.com/software/integration/support/supportpacs/category.html#cat2
MS03: WebSphere MQ - Save Queue Manager object definitions using PCFs
Otherwise, investigate a mirrored DSAD solution, or; if you are using AIX, the HACMP supportpac...
MC63: WebSphere MQ for AIX - Implementing with HACMP
Maybe explain what your goal is, that has you trying this experiment. I'd like to understand what you are trying to accomplish. Thank you, Chris
--- "Kulbir S. Thind" <[EMAIL PROTECTED]> wrote:
> 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.
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
