Using The Retro Changelog Plug-In; Table 8-2 Attributes Of A Retro Changelog Entry - Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual

Repeat Step 7 and Step 8 for each read-only replica that will receive updates
9.
from a legacy supplier.
To complete your legacy replication setup, you must now configure the legacy
10.
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 Changelog Plug-in

The retro changelog plug-in enables you to configure Directory Server to maintain
a changelog that is compatible with the changelog implemented in Directory
Server 4.0, 4.1, and 4.1x. Maintaining a retro changelog is essential in deployments
where Directory Server coexists with the retired Netscape Meta Directory
application. You might also need to maintain a retro changelog if you have
directory clients that depend on a Directory Server 4.x style changelog.
To use the retro changelog 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 changelog, this
changelog is stored in a separate database under a special suffix
The retro changelog consists of a single level of entries. Each entry in the changelog
has the object class
Table 8-2.
Table 8-2
Attribute
changeNumber
The 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
Attributes of a Retro Changelog Entry
Definition
This single-valued attribute is always present. It contains an
integer which uniquely identifies each change. This number is
related to the order in which the change occurred. The higher
the number, the later the change.
and can include the attributes listed in
Chapter 8
Using the Retro Changelog Plug-in
.
cn=changelog
Managing Replication 357