Sun Microsystems 8190994 manual Migrating a Replicated Topology to a New Topology

Migration Scenarios

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

6.0 Master A

5.x Master B

6.0 Hub A 6.0 Hub B

6.0 Consumer A 6.0 Consumer B

FIGURE 4–12Placing the 6.0 Master Into the Topology

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.

Migrating a Replicated Topology to a New Topology

Before you start migrating replicated servers, determine whether your deployment might not be better served by changing the architecture of the topology. This section describes how to migrate a basic version 5 topology to a new all-master topology. Migrating to an all-master topology involves migrating the consumers, hubs, and masters, then promoting the hubs to masters and the consumers to hubs, then to masters. The following sections demonstrate a sample migration of a simple multi-master topology to a new all-master topology.

The following figure shows the existing version 5 topology.

Chapter 4 • Migrating a Replicated Topology 63

Sun Confidential: Registered