LDAP how is Failover done?

[Ivan Avery Frey]

On 05/08/11 7:48, John Miles wrote:
> Hi,
>
> I need some direction on where to start with a solution for replacing some LDAP
> infrastructure.
>
> We presently have 1 LDAP server.
>
> My manager desires multiple LDAP servers (and so do I for failover/disaster recover)
>
> The largest issue appears to be keeping changes in user passwords in sync.
>
> What have you folks done to deal with that?
>
> Right now, there are 2 models we are debating:
>
> Model 1:
> 1 Master  - 3 slaves
> Build a scenario where 3 slaves are used for the largest volume (reading)
> * the exception would be password changes which would require updates directly
> on the Master
> * administration would be on the Master (i.e. by me, and my sysadmin friends)
>
> Model 2:
> 3 Masters - 3 way replication
> All 3 servers can be written to
> * the problem is keeping them in sync in cases where something is changed on
> one, and then on another between replication cycles.
>
> Anyone have experience setting up something like this?
>
> Thank you!
>
> John.

Have you considered clustering? We have a gtalug member who is an expert at that.

She's even posted a tutorial here: 
https://alteeve.com/w/Red_Hat_Cluster_Service_2_Tutorial

At first glance I prefer Model 1. Even for the postgres folk and Chris will 
correct me if I'm wrong, multi-mastering is a "hard" problem.

Ivan.
--
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