Sun Java System Directory Server Enterprise Edition 6.3 Migration Guide

Migrating the Masters

    For each master in the replicated topology:

  1. If you have client applications that write to the master you want to migrate, reroute these applications to write to another master in the topology.

  2. Ensure that the master is no longer receiving write requests. You can do this by enabling read-only mode on the master.

  3. Check that replication is synchronized between the master and all its consumers.

    Migration of the change log is not supported if you are migrating manually, so the preceding two steps are mandatory in this case. Although automatic migration does migrate the change log, you should still perform the above steps to avoid the risk of losing changes.

  4. Disable any replication agreements to and from the master you want to migrate.

  5. Stop the master.

  6. Migrate the master according to the instructions under Chapter 1, Overview of the Migration Process for Directory Server.

  7. Start the master.

  8. Enable the replication agreements from the master to the hubs and other masters in the topology.

  9. If you have migrated the data, check that replication is in sync.

  10. If you have not migrated the data, reinitialize the master from another master in the topology.

  11. If you rerouted client applications (Step 2), you can now route the applications to write to the migrated master.

The following sequence of diagrams illustrate the migration of a master, as described above. The first diagram shows the version 5 topology before the migration of the masters.

Figure 4–9 Existing version 5 Topology With Consumers and Hubs Migrated

Figure shows basic multi-master topology with 6.0 consumers
and hubs

The first step in migrating a master involves disabling replication agreements, effectively isolating the master from the topology.

Figure 4–10 Isolating the Master From the Topology

Figure shows master removed from topology

The next step involves migrating the version 5 master.

Figure 4–11 Migrating the version 5 Master

Figure shows migration of one master

The next step involves enabling the replication agreements to and from the new master and initializing the master if necessary.

Figure 4–12 Placing the 6.0 Master Into the Topology

Figure shows topology with one migrated master

Check that the replication on all hubs and consumers is in sync with the rest of the topology before migrating another master. A server that has just been migrated does not have a change log, and can therefore not update servers that are out of sync. Allow the topology to stabilize and all servers to synchronize before migrating the next supplier server.