Novell EDIRECTORY 8.8 - GUIDE, Manual

Page: 109 / 574

Managing Objects 109
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
Synchronization Method
Normally, eDirectory automatically chooses the method based on the number of replicas and
replication partners. The following are the synchronization methods:
• By Partition: The modifications to data are synchronized simultaneously with other
replicas.Several threads are used to synchronize the modifications. For example, D1, D2, and
D3 are modifications to data on replica R1, and these have to be synchronized across replicas
R2 and R3, D1, D2, and D3 are simultaneously synchronized with R2 and R3.
• By Server: Modifications to data are synchronized sequentially. Only one thread is used to
sync the modifications. For example, D1, D2, and D3 are modifications to data on replica R1.
These have to be synchronized across replicas R2 and R3, D1 is first synchronized with R2 and
R3. Then D2 is synchronized with R2 and R3.
• By Dynamic Adjust: Based on the system resources you have allotted, eDirectory
automatically chooses the synchronization method.
Using iMonitor, you can specify the method of synchronization using Agent Configuration under
Agent Synchronization . For more information, refer to “Controlling and Configuring the DS Agent”
on page 196 .
3.4.3 Priority Sync
Priority Sync is one of the two synchronization processes in eDirectory. In eDirectory 8.8 and later,
you can use priority sync when you need to sync your critical data immediately and cannot wait for
normal synchronization.
Priority sync is complimentary to the normal synchronization process in eDirectory. Unlike normal
synchronization, in priority sync, the changes are not buffered before synchronizing them across the
servers. This makes priority sync faster than normal synchronization.
Priority sync is enabled by default. Refer to “Enabling and Disabling Inbound and Outbound
Priority Sync” on page 110 for more information.
To sync the modifications to the critical data through priority sync:
1 Specify the number of threads for priority sync.
See “Priority Sync Threads” on page 110 for more information.
2 Specify the priority sync queue size.
See
“Priority Sync Queue Size” on page 110 for more information.
3 Create and define a priority sync policy by identifying the critical attributes that you want to
sync as priority.
See
“Creating and Defining a Priority Sync Policy” on page 112 for more information.
4 Apply the priority sync policy to one or more partitions.
See
“Applying a Priority Sync Policy” on page 113 for more information.
The priority sync process is to sync only the modifications to the critical attributes. If you create a
new object that has the critical attributes, the created object is not synchronized with other servers.
Priority sync maintains the object transaction model. So, if noncritical data is modified and is not yet
synchronized, and if the critical data is changed for the same entry, the noncritical data along with
critical data is synchronized.