Date: Tue, 30 Oct 2007 09:48:16 -0400 From: "Bob Johnson" <fbsdlists@gmail.com> To: "Stephen Allen" <p0036343@brookes.ac.uk> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: How to provide fail-over capability for servers? Message-ID: <54db43990710300648j436dfb91t5ba21d5c69af1b4c@mail.gmail.com> In-Reply-To: <47264FD7.2040807@brookes.ac.uk> References: <47264FD7.2040807@brookes.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
It depends on what type of services the servers offer. Mail servers, web servers, file servers, DHCP servers? SMTP (the mail protocol) for instance has built-in provisions for automatic failover. - Bob On 10/29/07, Stephen Allen <p0036343@brookes.ac.uk> wrote: > I'm completely new to this so some of my ideas may sound ludicrous... > please put me right where necessary! > > I will have 3 net-facing servers which must be available 24/7. I had > planned to have an additional box located in a different building on the > same site (in case of part power-outage) that will run VMware server and > host all the fail-over servers. > > What options are there for providing automatic fail-over capability? I > had thought of running a cron job every minute that would test for the > existence of the other server and assume its identity if it couldn't get > a reply, but it feels like a 'sub-optimal' way of doing it. > > Can anyone give me some ideas I should be looking at? > > Many thanks, > Steve :) > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54db43990710300648j436dfb91t5ba21d5c69af1b4c>