HP OSMS Blueprint: Directory Services on HP ProLiant Servers with SLES10

refreshAndPersist mode is used, the engine is always ready to handle persistent
synchronization messages from the master server.
Setting Up the Replication
The syncrepl method uses a slave-side replication engine. To set up a syncrepl replication in
refreshOnly mode, enable the syncrepl engine on the CDS slave server. Additionally, enable
the syncprov overlay feature on the CDS master server.
The following example provides the detailed steps required to set up a syncrepl replication for
contents under binddn ‘dc=example, dc=com’ in refreshOnly mode:
1. To configure the slave server's slapd.conf file, add the following contents:
database bdb
...
index entryCSN,entryUUID eq
syncrepl rid=1 provider=ldap://master_side_IP binddn=“dc=example,dc=com”
bindmethod=simple credentials=secret searchbase=“dc=example,dc=com”
type=refreshOnly interval=00:00:02:00
For more information, see the slapd.conf(5) manpage.
2. To enable the syncprov “overlay” feature on the master server, use the following
configuration in the master server's slapd.conf file:
moduleload syncprov.la
...
database bdb
...
index entryCSN,entryUUID eq
overlay syncprov
syncprov-checkpoint 100 10
syncprov-sessionlog 100
For more information, see the slapo-syncprov(5)manpage.
3. After setting the configurations, restart the master-side server and then restart the slave-side
servers.
At this point, the binddn directory contents of the slave server should be the same as the
master server. Adding or removing the corresponding contents on the master server leads
to the same results on the slave server after the ‘interval’ period.
Monitoring the Replication Status
There is no formal tool to monitor the syncrepl replication status. However, there are two methods
you can use to verify that the replication is complete.
• Use the slapd debugging level to view slapd debug information.
• Use the ldapsearch command and compare the contextCSN of the master and slave
servers. The syncrepl method stamps each write operation with a Change Sequence Number
(CSN). Each CDS server maintains a contextCSN attribute which records the largest CSN
stored. You can determine whether the replication is complete by comparing the contextCSN
for both the master and slave servers.
Using the slapd Debugging Level
Start the slave-side slapd process with debugging enabled, for this example set the debug level
to 'syncrepl consumer processing ' (level 16384), by entering the following command:
# /etc/init.d/cdssserver start –d 16384
Once a replication occurs, the message do_syncrep2: displays.
If a replication finishes, the following messages display:
18