Hi list, We're looking into a some techniques to have reliable fail over capability for our Nagios server. We were thinking about an active/passive setup, with the passive one to become alive when the primary node goes down.
We are looking to our options how to make sure the passive node has the latest state of the monitoring results. The documentations suggests to tackle this with nsca and ocsp (http://ussrvud-mon01/nagios/docs/redundancy.html). We are thinking to use drdb on a dedicated lan to sync the rrd's, config files and the nagios state and log files. This should, to our opinion, work relatively well. Are there any people doing something similar for the moment? If so, are there any constraints, tips or things to take into account? Thanks in advance, -- Jelle Smet http://www.smetj.net ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null