Novell EDIRECTORY 8.8 - GUIDE, Manual

Page: 111 / 574

Managing Objects 111
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
earlier entry in the queue is not successfully synchronized with one of the servers, it does not affect
the synchronization of the rest of the entries.
Figure 3-4
Priority Sync Queue
You can specify the priority sync queue size in iMonitor using Agent Configuration under Agent
Synchronization . For more information, refer to “Controlling and Configuring the DS Agent” on
page 196 .
During a priority sync process, if a number of modifications happen at short intervals, the queue
reaches its maximum size then, the queue expires and a new queue is formed. The modifications in
the older queue that are not yet synchronized, will be synchronized by normal synchronization.
The queue size for priority sync can vary from 0 to 232 - 1. By default, this value is 232 - 1. If the
Priority Sync queue size is set to 0, no modifications are synchronized through priority sync. These
modifications are synchronized by normal synchronization.
The value -1 implies unlimited queue size. -1 is 232 - 1. When a negative value is specified, for
example, -3, it means -3 = -1-2, which is 232 - 1-2.
Managing Priority Sync Policies
You can manage priority sync by creating and defining policies and applying them to partitions
through iManager or LDAP. You define a priority sync policy by identifying the attributes that are
critical.
NOTE: Plug-ins are available only in Novell iManager 2.5 and later.
Server 1
D1, D2, D3 ...
are modifications
to critical data
Server 2
Server 3
D1
D2
D3
D3
D2
D1
3
2
1
D1
D2
D3
.
.
.
Priority Sync
queue