HP-UX Directory Server 8.1 administrator guide

1. In the Directory Server Console, click the Configuration tab.
2. Select the Replication node, and click the Legacy Consumer Settings tab in the right pane.
3. Check the Enable Legacy Consumer checkbox.
This activates the fields in the Authentication box.
4. Specify the supplier bind DN that the legacy supplier server will use to bind to the consumer.
Optionally, specify a password at least 8 characters long.
5. Click Save.
6. Now configure legacy consumer settings for each replica that will receive updates from a
legacy supplier.
a. In the navigation tree, expand the Replication node, and select a replica that will receive
updates from the legacy supplier.
b. In the Replica Settings tab, select the Enable Replica and Updatable by a 4.x Replica
checkboxes.
These options are the only ones required for replication to work. Optionally, specify a
replica ID. It is not necessary to specify a supplier DN because the one specified in step
4 will be used.
c. Click Save.
7. Repeat step 6 for each read-only replica that will receive updates from a legacy supplier.
8. To complete the legacy replication setup, configure the legacy supplier to replicate to the
Directory Server 8.1 instance. For instructions on configuring a replication agreement on a
4.x Directory Server, refer to the documentation for the legacy Directory Server.
NOTE:
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 the Directory
Server can be configured as it should be after the migration and legacy consumer settings only
have to be active for the duration of the transition.
8.16 Using the Retro changelog plug-in
The Retro Changelog plug-in configures 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 to maintain a changelog for directory clients that depend on a
Directory Server 4.x-style changelog.
To use the retro changelog plug-in, the Directory Server 8.1 instance must be configured as a
single-master replica.
When the Directory Server is configured to maintain a retro changelog, this changelog is stored
in a separate database under a special suffix, cn=changelog.
The retro changelog consists of a single level of entries. Each entry in the changelog has the object
class changeLogEntry and can include the attributes listed in Table 8-5 “Attributes of a Retro
changelog entry”.
382 Managing replication