11.20. Replication with Earlier Releases

This section provides information on how to optimize replication with earlier releases of Directory Server.

11.20.1. Using Legacy Replication

Directory Server 9.0 can be involved in replication with earlier releases of Directory Server, providing the following conditions are met:
  • Directory Server 9.0 is a consumer.
  • The legacy suppliers can be Directory Server 4.0, 4.1, and 4.1x.
The following restrictions apply:
  • A legacy Directory Server and Directory Server 9.0 cannot update the same replica. However, this version of Directory Server can have different replicas, where one is supplied by a legacy Directory Server and the other is supplied by Directory Server 9.0.
  • Directory Server 9.0 cannot be a supplier for other replicas.
The main advantage of using Directory Server 9.0 as a consumer of a legacy Directory Server is to ease the migration of a replicated environment, especially since migration is not supported from 4.x servers to 9.0. For more information on migration, see the Directory Server Installation Guide.

11.20.2. Legacy Replication and Parent Object Classes

There is one important difference between the way that Directory Server 4.x servers handle replicated entries and the way that Directory Server 9.0 handles replicated entries. In Directory Server 4.x, entries could be added without specifying parent object classes, and when those entries were modified or replicated, the server would not automatically insert those parent object classes. For example, a user could be added with the inetorgperson object class, but not the top or person object classes:
dn: uid=jsmith,ou=People,dc=example,dc=com
objectclass: inetorgperson
uid: jsmith
cn: John Smith
sn: Smith
However, in Directory Server 9.0, the parent object classes are automatically added to the entry when the entry is added, modified, or replicated. This means that the entries will be slightly different on the Directory Server 4.x supplier and the Directory Server 9.0 consumer, because the Directory Server 9.0 entry will have the parent object classes:
 dn: uid=jsmith,ou=People,dc=example,dc=com
 objectclass: top  
 objectclass: person  
 objectclass: inetorgperson
 uid: jsmith
 cn: John Smith
 sn: Smith

11.20.3. Configuring Legacy Replication

To set up legacy replication:
  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 check box.
    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.
    1. In the navigation tree, expand the Replication node, and select a replica that will receive updates from the legacy supplier.
    2. In the Common Settings area, select the Enable Replica and Updatable by a 4.x Replica check boxes.
      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.
    3. 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 9.0 instance. For instructions on configuring a replication agreement on a 4.x Directory Server, see the documentation for the legacy Directory Server.


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.