|
| |
| Sun Java(TM) System Directory Server 5.2 2005Q1 Installation and Migration Guide | |
Chapter 5
Migrating a Replicated 5.x TopologyWhen upgrading replicated 5.x servers, you typically start with the consumers, continue with the hubs, and finish with the masters. This bottom-up approach involves interrupting only one server at a time, rather than interrupting an entire branch of the replication topology. The approach also helps you avoid potential custom schema synchronization issues between masters and consumers.
This chapter includes the following sections:
Upgrading 5.x Servers
- For each consumer in the existing topology, proceed according to the instructions under Chapter 3, "Upgrading and Migrating Data for a Single Directory Server Installation" or follow the links in Chapter 3, "Finding Patch Update Instructions" to upgrade the consumer.
- For each hub in the existing topology, proceed according to the same instructions to update the hub.
- For each master in the existing topology, proceed according to the same instructions to update the master.
Adding Additional ServersAfter completing the upgrade from the 5.x topology to the 5.2 topology, you may add additional masters, hubs, and consumers as required for the new topology.
Perform the following steps for each additional server.
- Follow the links in Chapter 1, "Finding Installation and Upgrade Instructions" to determine how to install the new server.
- Adjust replication agreements on the new server to fit the planned topology.
- Initialize replication on the new server.
Refer to the Directory Server Administration Guide for instructions on configuring replication agreements and initializing replication.
Upon completion of this procedure, the update process is complete. Clients may begin using servers in the upgraded replication topology.
Example 5.x Upgrade ScenarioConsider an upgrade for 5.x dual masters replicating to two hubs supplying two consumers. This section shows the steps performed to upgrade the topology to use 5.2 servers.
Note
In the figures that follow, solid arrows represent active replication. Dotted and dashed arrows represent interrupted replication. Dashed arrows alone represent instances being migrated.
Figure 5-1 shows the 5.x topology before the upgrade.
Figure 5-1 Existing 5.x Topology Example
The first step involves upgrading consumers. Figure 5-2 shows the resulting topology.
Figure 5-2 Example 5.x Consumer Upgrade Step
The next step involves upgrading hubs. Figure 5-3 shows the results.
Figure 5-3 Example 5.x Hub Upgrade Step
The next step involves upgrading masters. Figure 5-4 shows the results.
Figure 5-4 Example 5.x Master Upgrade - Step 3
Figure 5-5 shows the 5.2 topology following the upgrade. At this point, servers in the old topology may be retired, and new servers added to the 5.2 topology.
Figure 5-5 Example 5.2 Topology after Upgrading
Client requests are now directed to the 5.2 topology.
