< Previous | Contents | Next >
1.6. Replication
The LDAP service becomes increasingly important as more networked systems begin to depend on it. In such an environment, it is standard practice to build redundancy (high availability) into LDAP to prevent havoc should the LDAP server become unresponsive. This is done through LDAP replication.
Replication is achieved via the Syncrepl engine. This allows changes to be synchronized using a Consumer
- Provider model. The specific kind of replication we will implement in this guide is a combination of the
3 http://manpages.ubuntu.com/manpages/en/man5/slapd-config.5.html
following modes: refreshAndPersist and delta-syncrepl. This has the Provider push changed entries to the Consumer as soon as they're made but, in addition, only actual changes will be sent, not entire entries.