Sun Microsystems 8190994 manual Migrating the Masters, 8Placing the 6.0 Hub Into the Topology

Migration Scenarios

5.x Master A

6.0Hub A

6.0Consumer A

5.x Master B

5.x Hub B

6.0 Consumer B

FIGURE 4–8Placing the 6.0 Hub Into the Topology

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

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.

7.Start the master.

60 Sun Java System Directory Server Enterprise Edition 6.0 Migration Guide • March 2007

Sun Confidential: Registered