HP-UX Directory Server 8.1 administrator guide

[slapd]
...
ConfigFile = repluser.ldif example supplier bind DN entry
ConfigFile = changelog.ldif example changelog entry
ConfigFile = replica.ldif example replica entry
ConfigFile = replagreement.ldif example replication agreement entry
...
2. Install and configure the second Directory Server instance. For the second server,
server2.example.com, use the setup-ds.pl command, which installs a Directory
Server instance without installing a local Administration Server.
/opt/dirsrv/sbin/setup-ds.pl -f /tmp/server2.inf
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 suffix entry
ConfigFile = repluser.ldif example supplier bind DN entry
ConfigFile = changelog.ldif example changelog entry
ConfigFile = replica.ldif example replica entry
ConfigFile = replagreement.ldif 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 -D "cn=directory manager" -w secret -p 389 -h supplier1.example.com
dn: cn=ExampleAgreement1,cn=replica,cn="o=NetscapeRoot",cn=mapping tree,cn=config
changetype: modify
replace: nsds5beginreplicarefresh
nsds5beginreplicarefresh: start
4. Run 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.
/opt/dirsrv/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 “Enabling 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.1 can be involved in replication with earlier releases of Directory
Server, providing the following conditions are met:
• Directory Server 8.1 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 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.1.
• Directory Server 8.1 cannot be a supplier for other replicas.
The main advantage of using Directory Server 8.1 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, see the Directory Server Installation Guide.
To set up legacy replication:
8.15 Replication with earlier releases 381