Overview

slurpd provides replication services ``in band''. That is, it uses the LDAP protocol to update a slave database from the master. Perhaps the easiest way to illustrate this is with an example. In this example, we trace the propagation of an LDAP modify operation from its initiation by the LDAP client to its distribution to the slave slapd instance.

The following steps constitute a sample replication scenario:

1. An LDAP client starts up and connects to a slave slapd.

2. The LDAP client submits an LDAP modify operation to the slave slapd.

3. The slave slapd returns a referral to the LDAP client, which causes the client to send the modify operation to the master slapd.

4. The master slapd performs the modify operation, writes out the change to its replication log file and returns a success code to the client.

5. The slurpd process notices that a new entry has been appended to the replication log file, reads the replication log entry, and sends the change to the slave slapd via LDAP.

6. The slave slapd performs the modify operation and returns a success code to the slurpd process.