Red Hat DIRECTORY SERVER 7.1 SP7 - S Guía para resolver problemas descargar pdf (Pagina 54)

54 Novell eDirectory 8.8 SP7 Troubleshooting Guide

removed after the Primary obituary is ready to be removed or, in the case of

Inhibit_move

, the

Tracking obituary is removed after the Primary obituary has moved to the

OBF_NOTIFIED

state on the

master replica.

The replica responsible for processing obituaries does so on a background process (the Obituary

Process), which is scheduled on a per-partition basis after a given partition finishes an inbound

synchronization cycle. If there are no other replicas of the partition, the Outbound Replication

Process is still scheduled on the heartbeat interval. The Outbound Replication Process then starts the

Obituary Process. The Obituary Process cannot be manually scheduled, nor does it need to be. As

synchronization occurs, the transitive vectors are updated, thus advancing the Purge Vector and Obit

Vector. As these vectors move forward, the obituary states are allowed to move forward. This,

together with the automatic scheduling done upon inbound synchronization, completes the obituary

processing cycle. Therefore, the lifeblood of obituary processing is object synchronization.

For an object that is being removed, after all obituaries whose associated Primary obituary is of type

Dead have been advanced to the last state (Purgeable), and that state has been synchronized to all

replicas, a new process is responsible for removing the remaining entry husk from the database. The

Purge Process runs automatically to remove these husks. You can manually schedule the Purge

Process and modify its automatic schedule interval by using the Agent Configuration page in

iMonitor.

9.1 Examples

This section contains the following examples:

 “Deleting an Object” on page 54

 “Moving an Object” on page 55

9.1.1 Deleting an Object

1 Add the Primary obituary OBT_DEAD.

The Back Link attribute contains a list of servers that have an interest in this object and need to

be notified of changes to this entry. For every DN listed in the Back Link attribute and all servers

listed in the entry's partition replica attribute, eDirectory adds a Back Link obituary. The creation

time of the Primary obituary, OBT_DEAD, is stored in the Secondary obituary.

The Used By attribute contains a list of partitions that have an interest in this object and need to

be notified of changes to this entry. For every DN listed in the Used By attribute, eDirectory adds

a Used By obituary. The creation time of the Primary obituary, OBT_DEAD, is stored in the

Secondary obituary.

2 Remove all attributes but the obituaries.

The Outbound Replication Process then synchronizes this change to all other servers in the

replica ring.

On the next inbound synchronization of this partition, the Obituary Process is started, which

does the following:

 Computes a time vector which is a minimum transitive vector, referred to as the purge

vector. Later versions of eDirectory compute a second minimum vector, called the obituary

vector, which does not consider replicas which are subordinate references.

 Each Obituary in this partition is now examined.

If the obituary is a Primary obituary, there are no Secondary obituaries, and the attribute's

modification time (MTS) on the obituary is older than the Purge Vector, then all servers

have seen the change and this obituary will be removed.

1 2 ... 49 50 51 52 53 54 55 56 57 58 59 ... 119 120

Comentarios a estos manuales

Sin comentarios

Red Hat DIRECTORY SERVER 7.1 SP7 - S Guía para resolver problemas Pagina 54

Comentarios a estos manuales

Relacionado con productos y manuales para Teléfonos Red Hat DIRECTORY SERVER 7.1 SP7 - S