[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: OpenLDAP 2.4 replication to a write-only LDAP server
- To: "'Gavin Henry'" <ghenry@suretecsystems.com>
- Subject: RE: OpenLDAP 2.4 replication to a write-only LDAP server
- From: "Brouwer, Onno - Acision" <onno.brouwer@acision.com>
- Date: Wed, 1 Oct 2008 03:20:21 +0200
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: "'openldap-technical@openldap.org'" <openldap-technical@openldap.org>
- Content-language: en-US
- In-reply-to: <48CE84FB.8070208@suretecsystems.com>
- References: <B6EF6E3E2A7C3345B53EDDB627A263C07E59DC79@ng-ex-mbx01> <48CE84FB.8070208@suretecsystems.com>
- Thread-index: AckXS0CdXoAVY87lRemawgj8IfAEdgMF6HOw
- Thread-topic: OpenLDAP 2.4 replication to a write-only LDAP server
Hi,
I got replication working towards the clients, sorta...
I want to have a fully redundant setup, but I now see duplicate errors on the slaves.
My setup is like this:
Master1--Slave1
| \/
| /\
Master2--Slave2
The masters are setup in mirror mode, and I have delta syncrepl between the masters and the slaves.
I now also see two contextCSNs maintained on all servers, one for each master. However when I now
make a change on e.g. master1, the change get propagated twice, once by each master, resulting in
duplicate errors on the slave side. How I can have a redundant replication without duplicates?
Regards,
Onno Brouwer
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.