Cluster Context; Partitioning And Replication; Objects Created By The Bcc Drivers For Identity Manager; Landing Zone - Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual

Table of Contents

3.6.2 Cluster Context

Place each cluster in a separate Organizational Unit (OU). All server objects and cluster objects for a

given cluster should be in the same OU.

Cluster Resources in Separate OUs

Figure 3-1

Partition the cluster OU and replicate it to dedicated eDirectory servers holding a replica of the

parent partition and to all cluster nodes. This helps prevent resources from being stuck in an NDS

Sync state when a cluster resource's configuration is modified.

When a resource is BCC-enabled, its configuration is automatically synchronized with every peer

cluster in the business continuity cluster by using customized Identity Manager drivers. The

following eDirectory objects are created in each peer cluster:

Cluster Resource object

Virtual Server object

Cluster Pool object

Cluster Volume object

The Cluster Resource object is placed in the Cluster object of the peer clusters where the resource

did not exist initially. The Virtual Server, Cluster Pool, and Cluster Volume objects are stored in the

landing zone. Search-and-replace transform rules define cluster-specific modifications such as the

IP address.

Any OU can be defined as the BCC landing zone. Use a separate OU for the landing zone than you

use for a cluster OU. The cluster OU for one peer cluster can be the landing zone OU for a different

peer cluster.

Planning a Business Continuity Cluster

Table of Contents

Do you have a question about the BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION and is the answer not in the manual?