Replication Agreement; Compatibility With Earlier Versions Of Directory Server - Netscape DIRECTORY SERVER 6.01 - ADMINISTRATOR Administrator's Manual

Replication Agreement

Directory Servers use replication agreements to define their replication
configuration. A replication agreement describes replication between one supplier
and one consumer only. The agreement is configured on the supplier server. It
specifies:
• The database to be replicated
• The consumer server to which the data is pushed
• The times during which replication can occur
• The DN and credentials that the supplier server must use to bind (called the
Replication Manager entry or supplier bind DN
• How the connection is secured (SSL, client authentication)
Compatibility with Earlier Versions of Directory
Server
The replication mechanism in this version of Directory Server is different from the
mechanism used in earlier versions of Directory Server. Compatibility is provided
through the:
• Legacy Replication Plug-in
• Retro Changelog Plug-in
The legacy replication plug-in makes Directory Server behave as a 4.x directory
server in a consumer role. For information on how to implement legacy replication
using this plug-in, refer to "Replication with Earlier Releases," on page 316.
The retro change log plug-in can be used when you want a Directory Server
supplier to maintain a 4.x style change log. This is sometimes necessary for
applications, such as Netscape Meta Directory, that have a dependency on the
Directory Server 4.x change log format, because they read information from the
change log. For more information on the retro change log plug-in, refer to "Using
the Retro Change Log Plug-In," on page 318.
Replication Overview
Chapter 8 Managing Replication 277