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

278 Novell eDirectory 8.8 Administration Guide
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
Process Description
Replica synchronization Ensures that changes to eDirectory objects are synchronized among all
replicas of the partition. This means that any server that holds a copy of a
given partition must communicate with the other servers to synchronize a
change.
Two types of replica synchronization can occur:
• Immediate sync occurs after any change to an eDirectory object or
any addition or deletion of an object in the directory tree.
• Slow sync occurs for specific changes to an eDirectory object that are
repetitive and common to multiple objects, such as changes to login
properties. Some examples of this are updates to Login Time, Last
Login Time, Network Address, and Revision properties when a user
logs in or out.
The slow sync process runs only in the absence of an immediate sync
process. By default, immediate sync runs ten seconds after any change is
saved and slow sync runs 22 minutes after other changes are made.
Schema synchronization Ensures that the schema is consistent across the partitions in the directory
tree and that all schema changes are updated across the network.
This process runs once every four hours by default.
Heartbeat Ensures that directory objects are consistent among all replicas of a
partition. This means that any server with a copy of a partition must
communicate with the other servers holding the partition to check the
consistency.
This process runs by default once every 30 minutes on every server that
contains a replica of a partition.
Limber Ensures that a server’s replica pointer table is updated when that server’s
name or address is changed. Such changes occur when
• The server is rebooted with a new server name or IPX TM internal
address in the
autoexec.ncf
file.
• An address is added for an additional protocol.
When a server is booted, the limber process compares the server’s name
and IPX address with those stored in the replica pointer table. If either is
different, eDirectory automatically updates all replica pointer tables that
contain a listing of that server.
The limber process also checks that the tree name is correct for each
server in a replica ring.
Limber runs five minutes after the server boots up and then every three
hours.
Backlink Verifies external references, which are pointers to eDirectory objects that
are not stored in the replicas on a server. The backlink process normally
runs two hours after the local database is opened and then every 13 hours
thereafter.