Please stop posting the same exact thing on a daily basis. Sending multiple posts on consecutive days is *not* going to help you. Quite the opposite, in fact.
On Thu, 2008-06-12 at 20:32 +0200, Frederik Vanhee wrote: > Hello, > > I'm thinking about a hardware upgrade of my Nagios server. > I have a setup with 1500 hosts and 9000 services (from which 2500 > services are active and the other 6500 passive). > I use the 'classic' Nagios interface for consulting + the Nagvis > frontend with the ndo backend. > In addition, I use Nagiosgrapher for graphing purposes. > > Now I'm in doubt if I would split the Nagios server in two servers : > > -one for the Nagios process + webinterface + nagiosgrapher > -second as database-server for the ndo-backend > > Or maybe another configuration ? > Would it be more interesting to invest in one server with more RAM and > more powerful cpu's or is it more interesting to split it into two servers ? > > Any suggestions, > > Vanhee Frederik > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > 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 ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ 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
