Migrating A Replicated 4.X Site - Approach 1 - Netscape DIRECTORY SERVER 6.1 Installation Manual

Migration Procedure

Migrating a Replicated 4.x Site - Approach 1

Given the constraints, an approach to migrating a replication topology of 4.x
servers is to:
Install the 6.x Directory Server and configure it both:
1.
Configure the 4.x supplier to send updates to the 6.x Directory Server.
2.
Upgrade 4.x consumer servers to Directory Server 6.x, and change their
3.
supplier server to be the Directory Server 6.x that you configured in Step 1.
This Directory Server now acts as a hub supplier.
Retire the 4.x supplier.
4.
The Directory Server 6.x that you configured in Step 1 is now the only supplier
in the topology.
To better understand Approach 1, consider a fairly simple replication topology:
• One supplier server, ServerA.
• Two consumer servers, ServerB and ServerC.
• ServerA has a supplier-initiated replication agreement to ServerB and to
ServerC.
• ServerA, ServerB, and ServerC are 4.x Directory Servers.
NOTE
To migrate this topology using Approach 1, follow these steps:
Install Directory Server 6.x on a new server, ServerD.
1.
88 Netscape Directory Server Installation Guide • August 2002
As a read-write replica, the role the server will fulfill once the migration
process is completed, that logs changes.
As a legacy consumer, the role the server must play during the migration
process.
You can migrate a topology where ServerB and ServerC have
consumer initiated replication (CIR) agreements with ServerA.
However, you cannot have CIR agreements in the new replication
environment because Directory Server 6.x does not support
consumer-initiated replication.