Novell EDIRECTORY 8.8 - GUIDE, Manual, Page: 107 / 574

Managing Objects 107
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
through Server 2. Server 3 lets Server 2 know that it has received the changes. Server 2 in turn tells
Server 1 that Server 3 and itself are synchronized.
Object Transaction Model
Synchronization in eDirectory maintains the object transaction model, a standard for LDAP and
X.500-compliant directories. Object transaction model means that all the previous transactions
should be synchronized before synchronizing the new ones.
For example, you have modifications D1, D2, and D3 to the data on a server. Due to network failure,
these modifications are not synchronized across other servers. If you make another modification D4
on the server, D4 will be synchronized only after D1, D2, and D3 are synchronized across all the
servers in the replica ring.
Transitive Vector
A transitive vector is a time stamp for a replica. It is made up of a representation of the number of
seconds since a common specific point in history (January 1, 1970), the replica number, and the
current event number. Here's an example:s3D35F377 r02 e002
For more information, refer to “Transitive Vectors and the Restore Verification Process” on
page 387 .
Local Received Up To
Local Received Up To (LRUT) is the time before which the local replica has received the changes.
For more information, refer to “Browsing Objects in Your Tree” on page 200 .
Remote Received Up To
Remote Received Up To (RRUT) is the LRUT of the remote replica.
For more information, refer to “Browsing Objects in Your Tree” on page 200 .
3.4.2 Normal or Replica Synchronization
Normal or Replica Synchronization is one of the two synchronization processes in eDirectory.
Normal synchronization synchronizes all the modifications to data on a server with other servers in
the replica ring.
Normal synchronization happens across all servers having any version of eDirectory, having the
same partition.
For more information, refer to Section 5.5, “Administering Replicas,” on page 133 .
You can enable or disable normal synchronization by enabling or disabling outbound and inbound
synchronization in Novell iMonitor. Both inbound and outbound synchronizations are enabled by
default. To sync the modifications to data across the other servers through normal synchronization,
you need to configure the synchronization parameters in iMonitor. Refer to
“Controlling and
Configuring the DS Agent” on page 196 for more information.
In normal synchronization, when you make any modifications to the data, the changes you make are
buffered before synchronizing them across the servers. You can view the synchronization status in