Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have critical servers (webservers and databases) that are fully replicated, except for the reverse proxy that we use to hide the internal stuff. This proxy is acting like a router that filters and redirects traffic to the main server and switch for failover if the main one is down.

We want to find an alternative to this proxy because one single entry point is not enough.

Is there any company that has a solid and redundant infrastructure that offers redirection to an IP and allows quick switching to another one?

share|improve this question

closed as off-topic by Bryan, mdpc, Dave M, Falcon Momot, Tim Brigham Aug 13 '13 at 14:44

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking product, service, or learning material recommendations are off-topic because they tend to become obsolete quickly. Instead, describe your situation and the specific problem you're trying to solve." – Bryan, mdpc, Dave M, Falcon Momot, Tim Brigham
If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 2 down vote accepted

You could go with a multi-load balancer solution with a virtual IP (VIP). This would be my suggestion if you're referring to systems at the same location. (you did not specify where you were replicating to)

share|improve this answer

This is often solved on-the-cheap by having round-robin DNS entries pointing to all of your Reverse-Proxies (plural). You can of course solve this with big dollars (BigIP, F5, etc), but you have to decide what your budget looks like.

If you're not using them already, you should look into Varnish, NGINX, HAProxy, and possibly Apache Traffic Server (which is not the same as the Apache Web Server).

share|improve this answer

Two things to consider: haproxy, especially since you are using HTTP (and maybe HTTPS) which it is originally designed for. That solves your failover-problem.

The other thing is heartbeatd, which (when installed and configured right) should help you have your one external resource (the incoming IP) accessible through multiple servers (well, one at the time, but if one goes down another can take over, which solves this).

haproxy can be found here:

heartbeatd is here:

share|improve this answer

'RSF-1' from fails over the vip associated with the service, and the framework as a whole is pretty flexible

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.