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.

Figure 4–13 Existing version 5 Topology

Migrating All the Servers

The first step is to migrate all the servers individually, as described in Migrating a Replicated Topology to an Identical Topology. The resulting topology is illustrated in the following figure.

Figure 4–14 Existing Topology With Migrated Servers

Promoting the Hubs

The next step involves promoting the hubs to masters, and creating a fully-meshed topology between the masters. To promote the hubs, follow the instructions in Promoting or Demoting Replicas in Sun Java System Directory Server Enterprise Edition 6.2 Administration Guide.

The following diagram illustrates the topology when the hubs have been promoted.

Figure 4–15 Migrated Topology With Promoted Hub Replicas

Promoting the Consumers

The next step involves promoting the consumers to hubs, and then to masters, and creating a fully-meshed topology between the masters. To promote the consumers, follow the instructions in Promoting or Demoting Replicas in Sun Java System Directory Server Enterprise Edition 6.2 Administration Guide.

The following diagram illustrates the topology when the consumers have been promoted.

Figure 4–16 New Fully-Meshed All-Master Topology