Novell Doc: BCC 1.2: Administration Guide for OES 2 SP1 Linux

D.2 Cluster2 to Cluster1

Next, create a second driver instance on the Identity Manager node for the second cluster in order to synchronize information from the second cluster to the first cluster.

Clusters for This Driver Instance

Clusters Synchronized by This Driver Instance	Value
Name of the source cluster Example: cluster2
Name of the destination cluster Example: cluster1

Clusters Synchronized by This Driver Instance

Value

Name of the source cluster

Example: cluster2

Name of the destination cluster

Example: cluster1

New Driver Set for the Source Cluster

Driver Set Information	Value
Name of the BCC driver set for the source cluster Example: Cluster2 BCC Driver Set
Context that contains the source cluster Example: cluster2.clusters.siteB.example HINT:Browse to select the context.
Distinguished name of the Identity Manager node in the source cluster Example: cl2svr1.cluster2.clusters.siteB.example HINT:Browse to select the server.
Create a new partition on this driver set	Deselect this option.

Driver Instance for the Connection from Source to Destination

Driver Set Information	Value
Preconfigured driver template to import (pick the same one that you selected for the Cluster1-to-Cluster2 synchronization): BCCClusterResourceSynchronization.xml UserObjectSynchronization.xml HINT:The User Object Synchronization driver is needed only when creating a driver instance for communications between clusters in different trees. In this case, create one driver instance for resource synchronization and one driver instance for user object synchronization.
Driver name for this driver instance Example: cluster2_to_cluster1 BCCCR Sync Example: cluster2_to_cluster1 BCCUO Sync Default: BCC Cluster Sync
SSL Certificate name for this driver instance Example: cluster2_to_cluster1 BCCCR Sync Example: cluster2_to_cluster1 BCCUO Sync Default: BCC Cluster Sync (kmo)
IP address or DNS name of the Identity Manager node in the destination cluster for this driver instance Example: 10.10.10.21 Example: cl1svr1.cluster1.clusters.siteA.example
Unique IP port to use for this driver instance (same as you used for the Cluster1-to-Cluster2 driver instance) Example: 2002 (default for resource sync) Example: 2001 (default for user object sync) HINT:Both clusters must use the same port for this connection.
Distinguished name of the source cluster for this driver instance Example: cluster2.clusters.siteB.example HINT:Browse to select the cluster.
Landing zone for this driver instance Specify the distinguished name of the container where the cluster-enabled pool, NCP server, and volume objects for the destination cluster will be placed when they are synchronized to the source cluster for this driver instance. The container must already exist and must be specified using dot format without the tree name. Example: clusters.siteB.example HINT:Browse to select the context.