Benjamin MALYNOVYTCH wrote:
**********************************
JK> Maybe you can just use two A records in your dns.
JK> Both point to one server, and both servers keep an eye on the other with
JK> hearthbeat,
JK> As soon as one of the servers gets unresponsive the other claims the ip
JK> as a secundary ip.
JK> ifconfig eth0 add otherip.
JK> // not forget to arp for it!
JK> And as soon as the hearthbeat finds the other server to be back online,
JK> it unsets the ip, and lets the other know that it can add the ip again.
JK> Not so hard, just a couple of shell scripts afaik.
JK> greets
JK> Jan
**********************************
This sounds pretty good, but the customer is running mysql with data
changing all day long. That means that I would have two seperate db,
one on each machine, without being able to merge/keep uptodate those
dabatases :/
Best regards,
Benjamin MALYNOVYTCH
That would be a different problem,
You should check mysql failover and master->slave replication. Mysql
replication should be handled as a different "project" as its something
of a bitch to setup reliably.
greets
Jan
--
[email protected] mailing list
