Hi List,
I am trying to set up replication from an OpenLDAP 2.4 master to a write-only LDAP slave. This slave is not really an LDAP slave, but has an LDAP interface to have changes replicated to it. In earlier OpenLDAP releases I could use slurpd for this, but since this has been deprecated I am trying to get it working using syncrepl. Based on what I found in the online manual I am trying to achieve this with an additional OpenLDAP 2.4 proxy which replicates changes it learns from the master through syncrepl to the slave through the LDAP backend. Is there some way I can get this to work? If the slave is a real LDAP server, then the proxy works, but it stores the contextCSN on the slave, and not on the proxy. If I have some form of storing this contextCSN elsewhere then I might try to start the proxy (in case it dies) with this contextCSN value specified on the command line. Also, when I try to ban searches on the slave (since it is a write-only slave), the proxy thinks none of the master entries exist on the slave and then happily tries to add them to the slave, resulting in duplicate errors.
Any help would be greatly appreciated!
Regards,
Onno
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.
Brouwer, Onno - Acision wrote:
Hi List,
I am trying to set up replication from an OpenLDAP 2.4 master to a write-only LDAP slave. This slave is not really an LDAP slave, but has an LDAP interface to have changes replicated to it. In earlier OpenLDAP releases I could use slurpd for this, but since this has been deprecated I am trying to get it working using syncrepl. Based on what I found in the online manual I am trying to achieve this with an additional OpenLDAP 2.4 proxy which replicates changes it learns from the master through syncrepl to the slave through the LDAP backend. Is there some way I can get this to work? If the slave is a real LDAP server, then the proxy works, but it stores the contextCSN on the slave, and not on the proxy. If I have some form of storing this contextCSN elsewhere then I might try to start the proxy (in case it dies) with this contextCSN value specified on the command line. Also, when I try to ban searches on the slave (since it is a write-only slave), the proxy thinks none of the master entries exist on the slave and then happily tries to add them to the slave, resulting in duplicate errors.
Any help would be greatly appreciated!
Did you see http://www.openldap.org/doc/admin24/replication.html#Push%20Based
This info will be updated online soon, but the cvs version is.
It can also be achieved without a seperate proxy.
Thanks.
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.
openldap-technical@openldap.org
-
Brouwer, Onno - Acision -
Gavin Henry