Hi folks, What's the verdict on configuring both Live and Failover to use a single SQL database to store Inciga state and working configuration?
This way, when the Failover Icinga starts up it knows everything the Live did prior to crashing; failed checks, escalations, acknowledgements, etc. Better yet; have each Icinga server use their own end of a replicated PostgreSQL DB, that way the DB master can switch depending on which Icinga instance is active and state information if kept current on failback. Not knowing Icinga too well, I'd like to know whether there are any obvious problems with this idea (i.e. the two Icinga instances playing badly with essentially a single database). This kinda came up in a post a few months back; but someone suggested throwing drdb into the mix as well. Any thoughts would be really appreciated. Cheers, C ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
