Migrating Sun Java Directory Server to HP-UX Directory Server White Paper
16
migrated from SJDS (as described in the “Data migration” section), or data that has been exported
from another HPDS replica.
Note:
For synchronizing replicated HPDS instances, this white paper describes a
method that involves importing the LDIF. This method is the easiest and
most straightforward. There are two additional methods for initializing a
replica. Creating a backup of the database files of one replica using the
db2bak command, and installing those database files into another replica
using the bak2db command with the –n option. Additionally, by setting a
replication agreement to perform an online initialization, a replica can
initialize another replica. Both of these methods are described in the
HP-UX
Directory Server Administrator Guide in the section titled “Initializing
consumers”.
Both HPDS and SJDS use the same configuration elements for replication, but the administrator
interfaces differ. The SJDS administration interface performs much of the configuration in the
background; for example, it automatically creates a changelog configuration when a replication
agreement is added. In contrast, the HPDS administration interface requires creating a changelog
manually.
Note:
Although the replication agreements will be created at this point, the
replicas are not synchronized until the data migration is completed. Error
messages in the errors log will indicate that the replication protocol cannot
proceed, but those can be ignored for the moment.
For more information about these configuration steps, see the “Managing replication” chapter in the
HP-UX Directory Server Administrator Guide.
Use the following checklist for the high-level replication configuration steps to complete.