Replication with Earlier Releases
291
With server2, use the
inf
file to create and configure a
o=NetscapeRoot
database on
server2
as a multi-master supplier replica:
[slapd]
...
ConfigFile = netscaperootdb.ldif
Example 3.1, “Example Root Suffix Entry”
ConfigFile = repluser.ldif
Example 8.1, “Example Supplier Bind DN Entry”
ConfigFile = changelog.ldif
Example 8.2, “Example Changelog Entry”
ConfigFile = replica.ldif
Example 8.3, “Example Supplier Replica Entry”
ConfigFile = replagreement.ldif
Example 8.4, “Example Replication Agreement Entry”
...
3. Initialize the
o=NetscapeRoot
database on
server2
from
server1
. Add the
nsds5replicarefresh
attribute to the replication agreement on
server1
.
ldapmodify -h supplier1.example.com -p 389 -D "cn=directory manager" -w password
dn: cn=ExampleAgreement1,cn=replica,cn="o=NetscapeRoot",cn=mapping tree,cn=config
changetype: modify
replace: nsds5beginreplicarefresh
nsds5beginreplicarefresh: start
4. Run the
register-ds-admin.pl
to create a local Administration Server on
server2
and
switch the configuration directory for
server2
to its own
o=NetscapeRoot
database from
server1
.
/usr/sbin/register-ds-admin.pl
5. Disable the PTA Plug-in on
server2
so that it does not pass bind operations for the
administrative users in its
o=NetscapeRoot
to
server1
.
See
Section 16.2, “Enabling and Disabling Plug-ins”
.
8.15. Replication with Earlier Releases
This section provides information on how to optimize replication with earlier releases of Directory
Server. Directory Server 8.0 can be involved in replication with earlier releases of Directory Server,
providing the following conditions are met:
• Directory Server 8.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 8.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 8.0.
• Directory Server 8.0 cannot be a supplier for other replicas.
The main advantage of using Directory Server 8.0 as a consumer of a legacy Directory Server is to
ease the migration of a replicated environment. For more information on the steps to follow to migrate
a replicated environment, refer to the
Directory Server Installation Guide
.
Summary of Contents for DIRECTORY SERVER 8.0
Page 18: ...xviii ...
Page 29: ...Configuring the Directory Manager 11 6 Enter the new password and confirm it 7 Click Save ...
Page 30: ...12 ...
Page 112: ...94 ...
Page 128: ...110 ...
Page 190: ...Chapter 6 Managing Access Control 172 4 Click New to open the Access Control Editor ...
Page 224: ...206 ...
Page 324: ...306 ...
Page 334: ...316 ...
Page 358: ...340 ...
Page 410: ...392 ...
Page 420: ...402 ...
Page 444: ...426 ...
Page 454: ...436 ...
Page 464: ...446 ...
Page 484: ...466 ...
Page 512: ...494 ...
Page 522: ...504 ...