Enabling Replication on a Hub

Hub replicas act as both consumers and masters to further distribute replicated data to a larger number of consumers. Hub replicas receive replication updates from their suppliers and send replication updates to their consumers. They do not accept modifications, but instead return referrals to the masters.

Configuring a hub server consists of preparing an empty suffix to hold the replicated suffix and enabling replication on that suffix. Optional advanced configuration can include choosing a different replication manager, setting referrals, setting the purge delay, and modifying change log parameters.

The following sections explain how to configure one hub server. Repeat all procedures on each server that will contain a hub replicated suffix.

To Create a Suffix for a Hub Replica

If an empty suffix does not already exist, create it on the hub server with the same DN as the intended master replica.

For instructions, see Creating Suffixes.

If the suffix exists and is not empty, its contents will be lost when the replicated suffix is initialized from the master.

To Enable a Hub Replica

If you have hub replicas, enable them now.

You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.

Enable the hub replicated suffix.

$ dsconf enable-repl -h host -p port hub suffix-DN

For example:

$ dsconf enable-repl -h host1 -p 1389 hub dc=example,dc=com

To Modify Change Log Settings on a Hub Replica

For advanced hub configuration, the only parameters that you might want to modify are related to the change log. As a supplier, a hub server requires a change log.

You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.

To modify a change log setting on a hub, use one of the following commands:

$ dsconf set-server-prop -h host -p port suffix-DN repl-cl-max-age:value

$ dsconf set-server-prop -h host -p port suffix-DN repl-cl-max-entry-count:value