Service manual

(4.x to 5.2) Upgrading Replicated Servers
Chapter 2 Upgrading From Previous Versions 59
1. Proceed according to the instructions under “Upgrading a Single Server,” on
page 54 to upgrade the top server in the branch.
This cuts replication flow to the branch, temporarily bringing replication
updates on downstream servers in the branch to a halt.
2. Configure the replication agreement on the new server in the 5.2 branch to
receive updates from a 5.2 server closer in the replication topology to the new
master.
For example,configure the top server in the new branch to receive updates
from the 5.2 master.
3. Initialize replication from the 5.2 supplier to the new 5.2 server.
Depending on network capacity and volume of directory data compared to
updates, offline initialization may be faster than online initialization.
4. Apply Step 1, Step 2, then Step 3 recursively along the branch until you have
completed the steps for all leaf consumers.
Refer to the Sun ONE Directory Server Administration Guide for instructions on
configuring replication agreements and initializing replication.
At this point, the update process is complete for the branch. Repeat the procedure
for the remaining 4.x branches.
Adding Additional Servers
Aftercompleting the upgrade from the 4.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.
1. Proceed according to the instructions under Chapter 1, “Installing Sun ONE
Directory Server,” to install the new server.
2. Adjust replicationagreements on the new server to fit the planned topology.
Refer to the Sun ONE Directory Server Administration Guide for instructions.
3. Initialize replication on the new server.
Again, refer to the Sun ONE Directory Server Administration Guide for
instructions.