Example Replication Strategy For A Small Site; Example Replication Strategy For A Large Site - Netscape DIRECTORY SERVER 7.0 - DEPLOYMENT Deployment Manual

Defining a Replication Strategy
• Use the hub supplier to replicate to local sites throughout the enterprise.
Replicating to local sites helps balance the work load of your servers and your
WANs, as well as ensuring high availability of directory data. Assume that
you want to replicate to four sites around the country. You then have four
consumers of each hub supplier.
• At each site, replicate at least once to ensure high availability, at least for read
operations.
Use DNS sort to ensure that local users always find a local Directory Server
they can use for directory lookups.

Example Replication Strategy for a Small Site

Suppose your entire enterprise is contained within a single building. This
building has a very fast (100 MB per second) and lightly used network. The
network is very stable, and you are reasonably confident of the reliability of your
server hardware and OS platforms. Also, you are sure that a single server's
performance will easily handle your site's load.
In this case, you should replicate at least once to ensure availability in the event
your primary server is shut down for maintenance or hardware upgrades. Also,
set up a DNS round-robin to improve LDAP connection performance in the event
that one of your Directory Servers becomes unavailable.

Example Replication Strategy for a Large Site

Suppose your entire enterprise is contained within two buildings. Each building
has a very fast (100 MB per second) and lightly used network. The network is very
stable and you are reasonably confident of the reliability of your server hardware
and OS platforms. Also, you are sure that a single server's performance will easily
handle the load placed on a server within each building.
Also assume that you have slow (ISDN) connections between the buildings, and
that this connection is very busy during normal business hours.
128 Netscape Directory Server Deployment Guide • October 2004