Determining Level Of Service - Red Hat DIRECTORY SERVER 8.1 - DEPLOYMENT Deployment Manual

Chapter 2. Planning the Directory Data
Data Format
Email address Text
Table 2.3. Directory Data Characteristics

2.3.4. Determining Level of Service

The level of service provided depends on 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 the 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 the directory is deployed, so make
sure the initial design can meet the future needs.
For example, if the risk of total failure must be eliminated, use a multi-master configuration, where
several suppliers exist for the same data.
2.3.5. Considering a Data Master
A data master is a server that is the master source of data. Any time the same information is stored
in multiple locations, the data integrity can be degraded. A data master makes sure all information
stored in multiple locations is consistent and accurate. There are several scenarios that require a data
master:
• Replication among Directory Servers
• Synchronization between Directory Server and Active Directory
• Independent client applications which access the Directory Server data
Consider the master source of the data if there are applications that communicate indirectly with the
directory. Keep the processes for changing data, and the places from which the data can be changed,
as simple as possible. After deciding on a single site to master a piece of data, use the same site to
master all of the other data contained there. A single site simplifies troubleshooting if the databases
lose synchronization across the enterprise.
There are different ways to implement data mastering:
• Master the data in both the directory and all applications that do not use the directory.
Maintaining multiple data masters does not require custom scripts for moving data in and out of the
directory and the other applications. However, if data changes in one place, someone has to change
it on all the other sites. Maintaining master data in the directory and all applications not using the
directory can result in data being unsynchronized across the enterprise (which is what the directory
is supposed to prevent).
• Master the data in some application other than the directory, and then write scripts, programs, or
gateways to import that data into the directory.
Mastering data in non-directory applications makes the most sense if there are one or two
applications that are already used to master data, and the directory will be used only for lookups (for
example, for online corporate telephone books).
14
Size Owner
Many character IS department
Related to
User's entry