Best way to achieve redundancy?
I can see how to do this using DNS (I'm familiar with zoneedit.com's services) and monitoring with a couple of local machines. I think the best I could hope for is a five to ten minute switch, and that's if my clients' DNS propogates quickly for them.
Is there a better way, perhaps using IP addresses instead? I've seen a little discussion about high availablity setups, but not much detail for me to go on.
Or is this something I could hire Linode support to set up with a couple of their servers (hopefully on separate generators)?
2 Replies
The machines should have two connections (ethernet and null modem for example) to prevent a network error causing one to incorrectly think the other is down.
The switch time is something like 5 seconds.
Look at Heartbeat:
At work we are looking at Zeus's ZXTM which is essentially a commercial version of hearbeat with dispatching, web gui, and other niceties.
As to whether this is something Linode would want to setup for you, I'm not sure. IMHO if your application requires that kind of availability you probably don't want a virtual server anyway.
"IMHO if your application requires that kind of availability you probably don't want a virtual server anyway."
I'm not really looking for "high availability", just a way to automatically fail-over within 2-3 minutes without waiting for DNS to repropogate.
I'm looking now at http redirection and how that might help, or if it will confuse the web site visitors.
I have here the problem of my limited knowledge, and too many different technologies that might offer a solution.