ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

Configuration of Replication
A master and slave server must start out with an identical database.
Configure a replica and replogfile* entry on the master for each slave.
replica host=natches.morrison.iserv.net:389
binddn="cn=root, dc=morrison-ind,dc=com"
bindmethod=simple credentials=secret
replogfile /var/spool/ldap/replog
Configure an updatedn entry on each slave, identical to the updatedn
parameter you specified in the master replica entry:
updatedn "cn=root, dc=morrison-ind,dc=com"
To have the slave refer change requests to the master specify an updateref:
updateref ldap:\\estate1.whitemice.org
Operations that cannot be replicated are stored in a rejection log. slurpd can
be run in "oneshot" mode with the -o option to re-process a rejection log.
*You need one replogfile per database (not per replica), except in the case of differentiated replication
where one replogfile may serve multiple databases. Some documentation is ambiguous on this point.