LDAP how is Failover done?

[Alejandro Imass]

On Fri, Aug 5, 2011 at 7:48 AM, John Miles <jmiles242-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
> Hi,
>
> I need some direction on where to start with a solution for replacing some
> LDAP infrastructure.
>
> We presently have 1 LDAP server.
>

OpenLDAP?

> My manager desires multiple LDAP servers (and so do I for failover/disaster
> recover)
>

[...]

> Model 1:

[...]


OpenLDAP supports several replication models including n-way
replication, and should handle several thousand users on a single
sever without a hiccup. Unless your set-up is extremely huge your
proposed schemes seem overkill IMHO.

The easiest scheme in my experience is master -> slave where the slave
is just a passive warm stand-by server. When the master goes down,
just change the IPs and the config files and re-start the slave as
master while you fix the old master to create a new slave. The
downtime is minimal and it's easily automate-able, and there are no
other external components like an LDAP reverse proxy/balancer or
anything like that. The truth is, that unless you partition your DIT
and use referrals, etc. you will _always_ have a single point of
failure so many elaborate schemes are just complications that will
bite you down the line.

> Anyone have experience setting up something like this?
>

If it's OpenLDAP I could help out more.Is this only LDAP or LDAP + Samba ?

> Thank you!
>
> John.
>
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists