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.
The first step in migrating a master involves disabling replication agreements, effectively
isolating the master from the topology.
5.x Master A
5.x Master B
6.0 Consumer A
6.0 Consumer B
6.0 Hub A
6.0 Hub B
FIGURE 4–9
Existing version 5 Topology With Consumers and Hubs Migrated
Migration Scenarios
Chapter 4 • Migrating a Replicated Topology
61
Sun Confidential: Registered
Summary of Contents for Sun Java System Directory Server Enterprise Edition 6.0
Page 7: ...Index 145 Contents 7 Sun Confidential Registered...
Page 8: ...8 Sun Confidential Registered...
Page 10: ...10 Sun Confidential Registered...
Page 13: ...Examples EXAMPLE 7 1 Sample Export Configuration File 109 13 Sun Confidential Registered...
Page 14: ...14 Sun Confidential Registered...
Page 36: ...36 Sun Confidential Registered...
Page 68: ...68 Sun Confidential Registered...