Replication Scenarios
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-4 shows an example of cascading replication. This example shows a
simple cascading replication scenario. You can create more complex scenarios with
several hub suppliers.
Figure 8-4
294
Netscape Directory Server Administrator's Guide • December 2003
Cascading Replication
Need help?
Do you have a question about the NETSCAPE DIRECTORY SERVER 6.2 - ADMINISTRATOR and is the answer not in the manual?
Questions and answers