Archive for the 'changelog' Category

Sun Directory Server 5.2 6-Way MMR – part 4 – Creating the replication manager

Published by Mike on November 9, 2007 under changelog, ldap, replication, sun

In order to perform replication, a replication manager entry must exist on each replication consumer. A replication consumer is a directory server instance that is configured to accept changes from another directory server instance. This differs from a consumer directory server instance, which is configured to refer all updates to its (possibly multiple) master instance(s).

For the purposes here, in a controlled replication environment, a single replication manager is all that is needed. We will use the typical setting for this entry, cn=Replication Manager, cn=replication, cn=config

Create a replication manager for this instance.

Sun Directory Server 5.2 6-Way MMR – part 3 – Creating the changelog

Published by Mike on November 8, 2007 under changelog, ldap, replication, sun

In order to configure replication in Directory Server 5.2, a changelog database is required on each master and replication hub instance in the topology.

As each of the 6 instances in this topology are going to be master instances, each is required to have its own changelog.

To simply things (at the expense of performance for larger installations), I created the changelog database inside the filesystem path of the installation (ie: /opt/ldap/slapd-ds0) for each instance.

The paths I used for the changelogdb are as follows:

ds0: /opt/ldap/slapd-ds0/changelogdb
ds1: /opt/ldap/slapd-ds1/changelogdb
ds2: /opt/ldap/slapd-ds2/changelogdb
ds3: /opt/ldap/slapd-ds3/changelogdb
ds4: /opt/ldap/slapd-ds4/changelogdb
ds5: /opt/ldap/slapd-ds5/changelogdb

I also have posted instructions on how to create a changelogdb.

Creating the changelog in Directory Server 5.2

Published by Mike on November 7, 2007 under changelog, ldap, replication, sun

For a changelog to be created, either the parent directory of where the changelog is to be created needs to be owned (and writable!) by the directory server user, or the changelog directory itself needs to be owned by the directory server user. In the LDIF example below, the changelog is created in the installation directory (/opt/ldap/slapd-ds0) with the maximum number of active entries to keep in the changelog of 999999, and the maximum number of days to keep information in the changelog of 7d.

dn: cn=changelog5,cn=config
changetype: add
objectClass: extensibleObject
objectClass: top
cn: changelog5
nsslapd-changelogdir: /opt/ldap/slapd-ds0/changelogdb
nsslapd-changelogmaxentries: 999999
nsslapd-changelogmaxage: 7d

Create a file with the above contents and save it to disk (I saved mine as /tmp/createchangelogdb.ldif).

Update your directory server instance via ldapmodify to create the changelog database.

/usr/bin/ldapmodify -h host -p port -D ‘rootdn‘ -w ‘password‘ -c -f /tmp/createchangelogdb.ldif