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

For more information on creating the Replication Manager entry, refer to "Creating
the Supplier Bind DN Entry" on page 296.

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 6.x versions of Directory Server is different from the
mechanism used in earlier versions (4.x) of Directory Server. Compatibility is
provided through the following:
• Legacy Replication 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 335.
• Retro Changelog Plug-in—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 337.
Replication Overview
Chapter 8 Managing Replication 289