Migrating Sun Java Directory Server to HP-UX Directory Server White Paper

17
Table 3: Checklist for configuring replication
Step Written notes

Determine the replica role: single-
master, multi-master, hub, or
consumer
Role: Single-Master / Multi-Master / Hub / Consumer

For a Multi-Master, Hub, or
Consumer type replica, create a
supplier bind entry to allow other
replicas to update data on this
instance
Supplier DN (incoming):
__________________________________________________________________

If the replica is to be configured as
a Master or Hub (that is, it will
transmit updates to another replica),
configure a changelog
Changelog enabled: Yes / No

Create replication agreements if the
replica is a Master or a Hub
Agreement Name #1: _______________________________________
Host name / port: _______________________________________
Supplier DN (outgoing): _______________________________________
Replication Schedules: _______________________________________
Excluded Attributes: _______________________________________

Changelog trimming window Max age: __________________ Max entries: ___________________
Data Migration
Both SJDS and HPDS rely on the open source database software Berkeley DB for data storage.
However, because of differences in the data management techniques used by HPDS and SJDS, the
internal format of the index files differs. Therefore, the database files cannot be copied directly
between the two products. Instead, transfer the data by exporting it into an LDIF file from the SJDS
instance, and then importing the data into the HPDS instance.
Additional steps are required to ensure that all data to be imported is compatible with HPDS. This
section describes the data migration procedure steps.
Note:
If multiple instances are being migrated and they are part of a replication
topology, then perform the following steps for the master instance only. For
more information, see the ”Replication considerations
” section.
The process to migrate data from SJDS to HPDS follows these steps:
1. Export the SJDS data into an LDIF file.
2. Collect password policy assignments and instance configuration information.
3. Produce an HPDS-compatible LDIF file from the SJDS LDIF created in step 1.
4. Import the converted LDIF file to HPDS.
5. If additional HPDS instances will participate in replication, export the LDIF for import into those
instances.