Netscape NETSCAPE DIRECTORY SERVER 6.02, Installation Manual

Page: 65 / 96

Migrating a Replicated Site
Chapter 6 Migrating From Previous Versions 65
The manual 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.0, 4.1, 4.11, 4.12, and 4.13 because
these releases of the Directory Server can replicate to a Directory Server 6.x
configured as a consumer.
The constraints, approach, and a summary of the steps involved in migrating a
replicated environment are provided below.
Constraints
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 a consumer of a 4.x Directory Server.
• The 6.x Directory Server must be configured as a legacy consumer.
• The replication agreement between the 4.x supplier server and the 6.x
consumer server must be a 4.x supplier-initiated replication agreement.
Approach
Given the constraints, the approach to migrating a replication topology of 4.x
servers is to:
1.
Install the 6.x Directory Server and configure it both:
❍
As a read-write replica that logs changes (the role the server will fulfill
once the migration process is completed)
❍
As a legacy consumer, (the role the server must play during the migration
process)
2.
Configure the 4.x supplier to send updates to the 6.x Directory Server.
3.
Upgrade 4.x consumer servers to Directory Server 6.x, and change their
supplier server to be the Directory Server 6.x that you configured in Step 1.
This Directory Server now acts as a hub supplier.