i would not recommend drdb or any of these low-level-replication-mechanism with an rdbms (or database-services like ldap etc) for master/slave/failover /cluster-scenarios.
please ban this from your mind as a solution. FOR!EVER! ;-) On 14/07/11 08:50, Michael Friedrich wrote: > Big_Edd wrote: >> Hello, >> >> Is it possible to configure failover monitoring, keeping the status of >> hosts and services (on PostgreSQL) persistent across master and slave? > > if you are using something like drbd/heartbeat for the postgresql > database where on the master fail, the slave start icinga and ido2db > e.g. then sure, it's possible. but i highly recommend to check drbd and > heartbeat from an external view too (and monitor that e.g. only the > master or only the slave are writing with ido2db to the postgresql > database). basically a failover setup for postgresql but enriched with > an monitoring application client to monitor itsself. > > kind regards, > michael > ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users
