Sun Microsystems 8190994 manual Migrating a Replicated Topology

C 4H A P T E R 4

Migrating a Replicated Topology

Directory Server Enterprise Edition 6.0 does not provide a way to migrate an entire replicated topology automatically. Migrating a replicated topology involves migrating each server individually. Usually, however, you should be able to migrate your entire topology without any interruption in service.

This chapter describes the issues involved in migrating replicated servers, and covers the following topics:

■“Overview of Migrating Replicated Servers” on page 51

■“Issues Related to Migrating Replicated Servers” on page 52

■“New Replication Recommendations” on page 53

■“Migration Scenarios” on page 54

Overview of Migrating Replicated Servers

Directory Server 6.0 supports an unlimited number of masters in a multi-master topology. This and other changes might mean that you redesign your topology rather than migrate to an identical topology with new servers. See Part III, “Logical Design,” in Sun Java System Directory Server Enterprise Edition 6.0 Deployment Planning Guide before continuing.

When migrating replicated version 5 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.

51

Sun Confidential: Registered