Installation guide

Migration Procedure
Chapter 6 Migrating and Upgrading From Previous Versions 99
[12/Jun/2002:10:33:51 -0700] - import backend3: Finished scanning file
"/export/home/jdoe/50-latest/slapd-bart/config//ldif/backend3.ldif" (2 entries)
[12/Jun/2002:10:33:51 -0700] - import backend3: Workers finished; cleaning up...
[12/Jun/2002:10:33:54 -0700] - import backend3: Workers cleaned up.
[12/Jun/2002:10:33:54 -0700] - import backend3: Cleaning up producer thread...
[12/Jun/2002:10:33:54 -0700] - import backend3: Indexing complete.
Post-processing...
[12/Jun/2002:10:33:54 -0700] - import backend3: Flushing caches...
[12/Jun/2002:10:33:54 -0700] - import backend3: Closing files...
[12/Jun/2002:10:33:54 -0700] - import backend3: Import complete. Processed 2
entries in 4 seconds. (0.50 entries/sec)
-------------------------------------------------------------------------
Migrate Changelog...
-------------------------------------------------------------------------
***** Migrate ReplicaBindDN entries...
-------------------------------------------------------------------------
***** Migrate MultiplexorBindDN entries...
****** End of migration ******
Migrating a 4.x Replicated Site
The procedure described in this section explains the migration path that you can
follow to migrate a replication topology of 4.x servers to a replication topology of
6.x Directory Servers.
You can migrate instances of Directory Server 4.x because these releases of the
Directory Server can replicate to a Directory Server 6.x configured as a
consumer. However, the following constraints must be observed in order to
successfully complete the migration of a replicated environment:
• The replication topology of legacy servers must be a valid topology.
• The new 6.x Directory Server must be configured as a legacy consumer of
the 4.x Directory Server, as explained in Chapter 8, “Managing Replication”
of the Netscape Directory Server Administrator’s Guide.
• The replication agreement between the 4.x supplier server and the 6.x
consumer server must be a 4.x supplier-initiated replication agreement.
The following sections summarize how you can migrate a replicated environment: