Using The Retro Change Log Plug-In - Netscape DIRECTORY SERVER 6.01 - ADMINISTRATOR Administrator's Manual

Using the Retro Change Log Plug-In

Click Save.
8.
Repeat Step 7 and Step 8 for each read-only replica that will receive updates
from a legacy supplier.
To complete your legacy replication setup, you must now configure the legacy
supplier to replicate to the Directory Server. For instructions on configuring a
replication agreement on a 4.x Directory Server, refer to the documentation for
your legacy Directory Server.
NOTE
Using the Retro Change Log Plug-In
The retro change log plug-in enables you to configure Directory Server to maintain
a change log that is compatible with the change log implemented in Directory
Server 4.0, 4.1, 4.11, 4.12, and 4.13. Maintaining a retro change log is essential in
deployments where Directory Server coexists with Netscape Meta Directory. You
might also need to maintain a retro change log if you have directory clients that
depend on a Directory Server 4.x style change log.
To use the retro change log plug-in, Directory Server must be configured as a
supplier server in a single-master replication scenario.
When you have configured Directory Server to maintain a retro change log, this
change log is stored in a separate database under a special suffix
The retro change log consists of a single level of entries. Each entry in the change
log has the object class
Table 8-2.
318 Netscape Directory Server Administrator's Guide • January 2002
Directory Server Console will not prevent you from configuring a
database as a read-write replica and enabling legacy consumer
settings. This makes migration easier because you can configure
your Directory Server as you want it to be after the migration, and
activate legacy consumer settings just for the duration of the
transition.
changeLogEntry
, and can include the attributes listed in
.
cn=changelog