The scripts are here:
the scripts provided do a remaster, audit to live, snapshot every run. we could modify it a bit to handle the inconsistency...
what's the use case behind remastering only when there is an inconsistency?
Just curious as to how flexible the scripting ability is for BladeLogic. I mean, if the audit comes back as consistent, then nothing that's monitored has changed, so there is no real reason for daily snapshots. Just for snapshots after an inconsistency is found.
Let me know if you see it differently
I just checked this out and it looks great - a great start but i don't think that it's exactly what i'm looking for.
I'm looking to schedule daily audit & snapshot jobs, and then change the master in the audit ONLY IF it returns inconsistent.
It seems as if this script will run the snapshot and (create a new??) audit for each component with the new snapshot as that master. Tell me if i'm reading this right - will this do this to every snap\audit job?
I'm sure that if it does, that there's a way to "play jazz" and hve it run against a specific snap\audit job and reverse it - run snap, run audit, if audit is incon, make new, latest snap the new master, re-run...
let me know what you think - thanks!
the scripting is pretty flexible. the script calls blcli commands (via jython) as the logic in the script dictates. so we could run the check every night but only take snapshots when you want to.
you'd need to flip the logic around.. so something like:
is there atleast 1 snapshot?
no -> take snapshot, create audit job
yes -> run audit of snapshot to live
is audit consistent?
yes -> do nothing
no -> take snapshot, reset master of audit job
it's just a matter of changing the script...
Time to go to school, son!!!!!