[SATLUG] Simple fail-over options
henry.pugsley at gmail.com
Wed Nov 14 11:32:44 CST 2007
Use Linux HA to handle the actual IP failover. With only 2 servers
you can end up with split-brain syndrome if the servers lose contact
with each other, so make sure you include a virtual node in the
cluster, such as the gateway IP address.
Use rsync to handle sync'ing files. Pick one server as the master,
and run a crontab that checks for updates and rsync them to the other
server if there are any changes.
If there is a MySQL database involved, you can setup circular
replication on both servers so you basically have a master-master
Ideally you would have at least 4 servers - 2 servers running HA and
LVS for load balancing, then 2 web/mysql nodes behind them.
On Nov 13, 2007 9:52 PM, Samuel Leon <leon36 at gmail.com> wrote:
> I need to get redundancy on a business webserver. Not really sure how
> to go about this. First I got to figure out the best way to keep the 2
> servers synced. And then I was thinking about maybe writing a bash
> script on server#2 or something that would ping server#1 every minute or
> so. Then if the ping times out, it will run another script to change
> its IP to server#1's IP. Seems like it would work as long as server#1
> is truly down and doesn't come back to life and we end up with 2 of the
> same IP's on the same network. Sound good or alittle too dirty?
> SATLUG mailing list
> SATLUG at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug to unsubscribe
> Powered by Rackspace (www.rackspace.com)
"The best way to predict the future is to invent it" - Alan Kay
More information about the SATLUG