Red Hat DIRECTORY SERVER 8.0, Руководство администратора

Страница: 280 / 552

Chapter 8. Managing Replication
262
NOTE
There can be multiple supplier bind DNs per consumer but only one supplier DN
per replication agreement.
g. Specify the URL for any supplier servers to which to refer updates.
By default, all updates are first referred to the supplier servers that are specified here. If no
suppliers are set here, updates are referred to the supplier servers that have a replication
agreement that includes the current replica.
In cascading replication, referrals are automatically sent to the hub server, which in turn refers
the request to the original supplier. Therefore, set a referral to the original supplier to replace
the automatically generated referral.
4. Click
Save
.
Repeat these steps for every consumer server in the replication configuration, then configure the hub
replica.
8.6.3. Configuring the Read-Only Replica on the Hub
Do this to set up a hub, which receives replication updates from the supplier and propagates them to
consumers:
1. Create the database for the read-only replica if it does not exist. See
Section 3.1.1, “Creating
Suffixes”
for instructions on creating suffixes.
2. Create the entry for the supplier bind DN on the consumer server if it does not exist. The supplier
bind DN is the special entry that the supplier will use to bind to the consumer. This is described in
Section 8.3, “Creating the Supplier Bind DN Entry”
.
3. Create the changelog for the hub server.
The hub must maintain a changelog even though it does not accept update operations because it
records the changes sent from the supplier server.
a. In the Directory Server Console, select the
Configuration
tab.
b. In the navigation tree, select the
Replication
folder.
c. In the right-hand side of the window, select the
Supplier Settings
tab.