Determining Level Of Service; Considering A Data Master - Netscape DIRECTORY SERVER 6.2 - DEPLOYMENT Deployment Manual

Table of Contents

Advertisement

Performing a Site Survey
For example, you can create a table that characterizes your directory data as
follows:
Table 2-3
Data
Employee Name
Fax number
Email address

Determining Level of Service

The level of service you provide depends upon the expectations of the people who
rely on directory-enabled applications. To determine the level of service each
application expects, first determine how and when the application is used.
As your directory evolves, it may need to support a wide variety of service levels,
from production to mission critical. It can be difficult raising the level of service
after your directory is deployed, so make sure your initial design can meet your
future needs.
For example, if you determine that you need to eliminate the risk of total failure,
you might consider using a multi-master configuration, in which several masters
exist for the same data. The next section discusses determining data masters in
more detail.

Considering a Data Master

The data master is the server that is the master source of data. Consider which
server will be the data master when your data resides in more than one physical
site. For example, when you use replication or use applications that cannot
communicate over LDAP, data may be spread over more than one site. If piece of
data is present in more than one location, you need to decide which server has the
master copy and which server receives updates from this master copy.
32
Netscape Directory Server Deployment Guide • December 2003
Directory Data Characteristics
Format
Text string
Phone number
Text
Size
Owner
128 characters
Human
resources
14 digits
Facilities
Many character
IS department
Related to
User's entry
User's entry
User's entry

Advertisement

Table of Contents
loading

This manual is also suitable for:

Directory server 6.2

Table of Contents