Preventing Identity Manager Synchronization Loops - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION Administration Manual

B.6 Preventing Identity Manager
Synchronization Loops
If you have three or more clusters each in separate eDirectory trees in your business continuity
cluster, you should set up IDM User object and Cluster Resource object synchronization in a manner
that prevents Identity Manager synchronization loops. Identity Manager synchronization loops can
cause excessive network traffic and slow server communication and performance.
For example, in a three-cluster business continuity cluster, an Identity Manager synchronization
loop occurs when Cluster One is configured to synchronize with Cluster Two, Cluster Two is
configured to synchronize with Cluster Three, and Cluster Three is configured to synchronize back
to Cluster One. This is illustrated in
Three-Cluster Identity Manager Synchronization Loop
Figure B-1
Cluster
IDM Sync
Cluster
Three
A preferred method is to make Cluster One an Identity Manager synchronization master in which
Cluster One synchronizes with Cluster Two, and Cluster Two and Cluster Three both synchronize
with Cluster One. This is illustrated in
Three-Cluster Identity Manager Synchronization Master
Figure B-2
Cluster
Cluster
Three
Figure B-1.
One
Cluster
Two
Figure B-2.
One
Cluster
Two
Implementing a Multiple-Tree BCC 131