Fail Safe Website?

We'd like to establish a website that is failsafe.

What I mean by this is to architect a series of redundant webservers and
replicated backends across multiple locations, in the event that one server
goes does, the system is smart enough to "roll-over" to one of the other
servers.

I know that Apache can be setup for load balancing, and MySQL has
replication capabilities, I guess the problem lays with A) how do we detect
the site has gone down (either backend or webserver), B) once the failure
has been detected, how do we redirect to a backup server, and C) if the
failed server comes back online for some reason (maybe the connection
hiccupped for some reason), how do we redirect back to the primary server
and make sure that all data is appropriately synchronized?

Any insight would be appreciated.

Chuck Sire wrote:
 > We'd like to establish a website that is failsafe.
 >
 > What I mean by this is to architect a series of redundant webservers
 > and replicated backends across multiple locations, in the event that
 > one server goes does, the system is smart enough to "roll-over" to
 > one of the other servers.

dns with v.short ttl

 > ... and make sure that all data is appropriately
 > synchronized?

how do you do it atm?


--
William Tasso - <a style='text-decoration: underline;' href="http://www.WilliamTasso.com" target="_blank">http://www.WilliamTasso.com</a><!-- ~MESSAGE_AFTER~ -->