Red Hat DIRECTORY SERVER 8.1 - DEPLOYMENT Deployment Manual page 70

Chapter 5. Designing the Directory Topology
If Example Corp. decided to spread their directory tree across five different databases, the new tree
would appear as follows:
Figure 5.4. Directory Tree Spread across Multiple Databases
The resulting suffixes would contain the following entries:
Figure 5.5. Suffixes for a Distributed Directory Tree
The o=NetscapeRoot and dc=example,dc=com suffixes are both root suffixes. The
ou=testing,dc=example,dc=com suffix, the ou=development,dc=example,dc=com suffix,
and the ou=partners,ou=development,dc=example,dc=com suffix are all subsuffixes of the
dc=example,dc=com root suffix. The root suffix dc=example,dc=com contains the data in the
ou=marketing branch of the original directory tree.
Using Multiple Root Suffixes
The directory service might contain more than one root suffix. For example, an ISP called "Example"
might host several websites, one for example_a.com and one for example_b.com. The ISP would
create two root suffixes, one corresponding to the o=example_a.com naming context and one
corresponding to the o=example_b.com naming context. The directory tree would appear as follows:
60