Configuring Multi-Master Replication
334
Red Hat Directory Server Administrator’s Guide • May 2005
d.
In the Common Settings section, specify a Replica ID.
The replica ID must be an integer between
1
and
254
, both inclusive, and
must be unique for a given suffix. Make sure you specify an ID that is
different from the IDs used for read-write replicas on this server and on
other servers.
e.
In the Common Settings section, specify a purge delay in the “Purge
delay” field.
This option indicates how often the state information stored in the
replicated entries is purged.
f.
In the Update Settings section, specify the supplier bind DN or entry DN
that the supplier will use to bind to the replica.
This supplier bind DN should correspond to the entry created in Step 2.
The supplier bind DN corresponds to a privileged user because it is not
subject to access control.
g.
Specify the supplier server to which you want to refer updates (the other
suppliers in the multi-master set).
Only specify the URL for the supplier server. If you want clients to bind
using SSL, you must specify a URL beginning with
ldaps://
.
h.
Click Save to save the replication settings for the database.
4.
Set up replication agreements on all the supplier servers:
❍
On server M1, set up the following replication agreements: one with
supplier server M2, where server M2 is configured as a
consumer
for the
replica; one with supplier server M4, where server M4 is configured as a
consumer
for the replica; and one for each consumer servers, Server C1
through Server C8.
❍
On server M2, set up the following replication agreements: one with
supplier server M1, where server M1 is declared as a
consumer
for the
replica; one with supplier server M3, where server M3 is declared as a
consumer
for the replica; and one for each consumer servers, Server C1
through Server C8.
❍
On server M3, set up the following replication agreements: one with
supplier server M2, where server M2 is declared as a
consumer
for the
replica; one with supplier server M4, where server M4 is declared as a
consumer
for the replica; and one for each consumer, Server C1 through
Server C8.
Содержание DIRECTORY SERVER 7.1
Страница 1: ...Administrator s Guide Red Hat Directory Server Version7 1 May 2005 Updated February 2009 ...
Страница 20: ...20 Red Hat Directory Server Administrator s Guide May 2005 Glossary 619 Index 635 ...
Страница 22: ...22 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 26: ...26 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 78: ...Maintaining Referential Integrity 78 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 200: ...Assigning Class of Service 200 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 278: ...Compatibility with Earlier Releases 278 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 374: ...Troubleshooting Replication Related Problems 374 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 478: ...Using the Management Information Base 478 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 488: ...488 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 528: ...PTA Plug in Syntax Examples 528 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 545: ...About Windows Sync Chapter 18 Windows Sync 545 Figure 18 1 Active Directory Directory Server Synchronization Process ...
Страница 572: ...572 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 586: ...Storing Information in Multiple Languages 586 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 606: ...Searching an Internationalized Directory 606 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 612: ...Examples of LDAP URLs 612 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 634: ...634 Red Hat Directory Server Administrator s Guide May 2005 ...