Cascading Replication - Netscape DIRECTORY SERVER 6.02 - ADMINISTRATOR Administrator's Manual

Table of Contents

Advertisement

Replication Scenarios
For information on setting up multi-master replication with two supplier servers
and two consumer servers, refer to "Configuring Multi-Master Replication," on
page 296.

Cascading Replication

In a cascading replication scenario, one server, often called a hub supplier, acts both
as a consumer and a supplier for a particular replica. It holds a read-only replica
and maintains a change log. It receives updates from the supplier server that holds
the master copy of the data, and in turn supplies those updates to the consumer.
Cascading replication is very useful when you need to balance heavy traffic loads
or have supplier servers based locally in geographically distributed environments.
Figure 8-3 shows an example of cascading replication. This example shows a
simple cascading replication scenario. You can create more complex scenarios with
several hub suppliers.
Chapter 8
Managing Replication
283

Advertisement

Table of Contents
loading

This manual is also suitable for:

Directory server 6.02

Table of Contents