Date: Sun, 23 Mar 2003 17:13:55 +0100 From: Eric Veraart <eric@monkey-online.net> To: freebsd-isp@freebsd.org Subject: Server redundancy over 2 co-locations Message-ID: <5.2.0.9.0.20030323164230.047f5650@mail.monkey-online.net>
next in thread | raw e-mail | index | archive | help
Hello, We currently have a few webservers at location 1, and are planning to place backup servers at location 2. Location 1 and 2 are seperated about 200km from each other. I want location 1 as the default location, and only put location 2 active when location 1 is down. This because location 2 is read-only, so the databases and documents on the two locations stay consistent. I've been looking at a few ways to achieve this; -The world famous F5 Networks 3-DNS controller; You pay for a lot of fancy things that I don't need, because it can ballance the connection over multiple locations, which I don't need. -Some sort of round-robin system, that runs on both locations (primary at location 1 and secondary at location 2) and checks if location 1 is still up, and otherwise points to location 2. I don't know if I'll get problems with TTL times, DNS caches etc with the round-robin system, or with the 3-DNS controller. What are your thoughts and experiences on this subject? Greetings, Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.2.0.9.0.20030323164230.047f5650>