JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Directory Server Enterprise Edition Deployment Planning Guide 11g Release 1 (
search filter icon
search icon

Document Information


Part I Overview of Deployment Planning for Directory Server Enterprise Edition

1.  Introduction to Deployment Planning for Directory Server Enterprise Edition

2.  Business Analysis for Directory Server Enterprise Edition

Part II Technical Requirements

3.  Usage Analysis for Directory Server Enterprise Edition

4.  Defining Data Characteristics

5.  Defining Service Level Agreements

6.  Tuning System Characteristics and Hardware Sizing

7.  Identifying Security Requirements

8.  Identifying Administration and Monitoring Requirements

Part III Logical Design

9.  Designing a Basic Deployment

10.  Designing a Scaled Deployment

11.  Designing a Global Deployment

12.  Designing a Highly Available Deployment

Availability and Single Points of Failure

Mitigating SPOFs

Advantages and Disadvantages of Redundancy

How Redundancy Handles SPOFs

Redundancy at the Hardware Level

Redundancy at the Software Level

Using Replication and Redundancy for High Availability

Using Redundant Replication Agreements

Promoting and Demoting Replicas

Using Directory Proxy Server as Part of a Redundant Solution

Using Application Isolation for High Availability

Sample Topologies Using Redundancy for High Availability

Using Replication for Availability in a Single Data Center

Using Replication for Availability Across Two Data Centers

Using Multiple Directory Proxy Servers

Using Application Isolation

Part IV Advanced Deployment Topics

13.  Using LDAP-Based Naming With Solaris

14.  Deploying a Virtual Directory

15.  Designing a Deployment With Synchronized Data


Chapter 12

Designing a Highly Available Deployment

High availability implies an agreed minimum “up time” and level of performance for your directory service. Agreed service levels vary from organization to organization. Service levels might depend on factors such as the time of day systems are accessed, whether or not systems can be brought down for maintenance, and the cost of downtime to the organization. Failure, in this context, is defined as anything that prevents the directory service from providing this minimum level of service.

This chapter covers the following topics: