MQSeries.net :: View topic

hopsala · Posted: Sun Jul 18, 2010 9:18 pm Post subject:

Hey guys, long time no see. Been traveling abroad. I'm back, for now

Anyway, I've been thinking up different crash and recovery scenarios for a client, and read all I could find but still couldn't find answers to a few nagging questions (these were especially helpful: Tool to save CM domain configuration & Is it worth backing up the Config Manager?)So here goes:

Let's say my CM crashes, and I have a day old backup. In the time passed between the backup and the crash, I've deployed one flow and deleted another. Now I recover BERNARD and... what? I imagine I simply won't see the extra deployed flow, but what of the deleted flow? I can bring things back into sync by re-deploying the new flow, but how do I resynch information about the deleted flow?
In general, what I'm trying get at up is that restoring the CM from a backup can create quite confusing inconsistencies - moved, deleted, created MFs, EGs, maps, JARs, not to mention collectives and pubsub info (and maybe something else?) - which could potentially be impossible to untangle. So other than a very clear manual log of deploys and version control, is there any other way to make sure a recovered CM can be resynched?

A second scenario: Say my broker crashes, and I recover from a day old backup. Now the same thing happens. The CM thinks the broker runs a flow it doesn't, and doesn't run a flow it does. What's the best way to resynch? I'm pretty sure this is equivalent to the previous scenario, but I may be missing something.

Lastly, in both situations I could adopt the broker, but this only syncs MFs and EGs, not maps, JARs, MRMs and adapter files. How do I resynch these entites? is redeploying the only option?

And yea, I know I can move to the wonderous omnipotent V7. I tried to explain to the client it will take him less time to make the upgrade than plan for recovery, but no such luck.