Here is the general layout we use keepalived to make sure the application is accessible in case of a failure keepalived uses VRRP ( Virtual Router Redundancy Protocol) to advertise a virtual IP from either the primary server or the secondary.  Both servers as you see from the diagram have their own IP but on top of that have a virtual IP they will use depending on their state. The user will connect to the virtual IP instead of the server IP so in the case of a failure, the user would not know they have switched servers. We use MariaDB replication to ensure that the databases are the same on both servers.

As of cacti, 1.x cacti support remote polling which allows you to have multiple servers act as pollers the remote pollers send the data to the main server that holds the graphs
this is a great solution for load balancing as well as the ability to have local pollers at remote locations to help with things like latency metrics.

Hey Everyone Just wanted to share some of my latest work  I have developed an interactive install wizard for Cacti written in BASH this script is currently written for Debian based systems but I am working on others Some of the main features are -download either chosen or latest version of cacti -autoconfigure database either

New Cacti install wizard Bash script on my GITHUBRead More »


Hey All just a quick post on WordPress authentication keys You may have noticed that in the newer versions of WordPress that in the WP-config.php file there is a block of code asking for key passphrases. That is to support encrypted cookies for your users when they login if you don’t generate the keys what

Dont forget to generate your wordpress secure cookie keys !Read More »