Hi list,
I've two servers running the same ldap service. A is primary server and B is
simply a mirror, and accounts from server A are constantly synchronized with
B.
Now I don't have a automatic failover solution, whenever server A goes down,
I have to point the domain's A record to server B
Per Qvindesland wrote:
Hi list,
I've two servers running the same ldap service. A is primary server and B is
simply a mirror, and accounts from server A are constantly synchronized with
B.
Now I don't have a automatic failover solution, whenever server A goes down,
I have to point the
Hi,
If it is a mission critical system, check out http://www.linux-ha.org/
I have that managing a cluster of servers for HA SQL. In your case you may
get away with just using a floating IP. Have the DNS pointing to that.
Then no matter what server the IP is on the DNS doesn't need to be
On Fri, Feb 20, 2009 at 1:29 PM, Per Qvindesland p...@norhex.com wrote:
I've two servers running the same ldap service. A is primary server and B is
simply a mirror, and accounts from server A are constantly synchronized with
B.
Now I don't have a automatic failover solution, whenever server
Hi All
Thanks for all your answers, I agree it would be better with heartbeat then
to mock around with dns and a very slow update time.
Regards
Per Qvindesland
On 2/20/09 2:08 PM, Tim Verhoeven tim.verhoeven...@gmail.com wrote:
On Fri, Feb 20, 2009 at 1:29 PM, Per Qvindesland p...@norhex.com
On Fri, 2009-02-20 at 15:36 +0100, Per Qvindesland wrote:
Hi All
Thanks for all your answers, I agree it would be better with heartbeat then
to mock around with dns and a very slow update time.
Regards
Per Qvindesland
Another benefit is that failover occurs much more quickly when using
6 matches
Mail list logo