Migrating A Replicated 4.X Site - Approach 2 - Netscape DIRECTORY SERVER 6.2 Installation Manual

To migrate this topology using Approach 1, follow these steps:
Install Directory Server 6.x on a new server, ServerD.
1.
Configure ServerD for the role it will fulfill in the migrated replication
2.
topology, that is as a read-write replica that logs changes.
This procedure is explained in Chapter 8, "Managing Replication" of the
Netscape Directory Server Administrator's Guide.
Then configure ServerD to be a legacy consumer.
3.
This procedure is explained in Chapter 8, "Managing Replication" of the
Netscape Directory Server Administrator's Guide.
Migrate ServerB to Directory Server 6.x following the instructions given in
4.
"Migrating a Standalone Server" on page 92.
Make ServerB a read-only replica of ServerD.
5.
This means that ServerD is now a hub supplier—it receives updates from
ServerA, and in turn updates ServerB.
Upgrade ServerC to Directory Server 6.x, and make it a read-only replica of
6.
ServerD.
Retire ServerA.
7.
Disable legacy consumer settings on ServerD.
8.
This leaves ServerD as the single supplier for consumer ServerB and ServerC.
When you have completed the migration of your replication topology, you can
evolve it to use multi-master replication. To do this, you must add a new
Directory Server 6.x that acts as a master to your replication topology. You
cannot change one of the read-only replicas to become a read-write replica.
For more information on multi-master replication topologies, see Chapter 8,
"Managing Replication" of the Netscape Directory Server Administrator's Guide.

Migrating a Replicated 4.x Site - Approach 2

Given the constraints, another approach to migrating a replication topology of 4.x
servers is to:
Shut down all writes to the directory.
1.
Migrate the master using the approach given in section "Migrating a
2.
Standalone Server" on page 92.
At this point, writes may resume to the master.
3.
Chapter 6 Migrating and Upgrading From Previous Versions
Migration Procedure
101