Cascading Replication - Netscape DIRECTORY SERVER 6.02 - DEPLOYMENT Deployment Manual

Table of Contents

Advertisement

Common Replication Scenarios
Replication Traffic in a Multi-Master Environment
Figure 6-3

Cascading Replication

In a cascading replication scenario, a hub supplier receives updates from a supplier
server, and replays those updates on consumer servers. The hub supplier is a
hybrid: it holds a read-only replica, like a typical consumer server and it maintains
a change log like a typical supplier server.
Hub suppliers do not actually keep copies of the master data themselves, they only
pass it on as it received it from the original master. For the same reason, when a
hub supplier receives an update request from a directory client, it refers the client
to the master server.
Cascading replication is useful, for example, if some network connections between
various locations in your organization are better than others. For example, suppose
the master copy of your directory data is in Minneapolis, and you have consumer
servers in Saint Cloud as well as Duluth. Suppose, too, that your network
connection between Minneapolis and Saint Cloud is very good, but your network
Chapter 6
Designing the Replication Process
103

Advertisement

Table of Contents
loading

This manual is also suitable for:

Directory server 6.02

Table of Contents