Perform an eDirectory Health Check
When and How Often Health Checks Are Needed
In general, if you network doesn’t change often (servers and partitions are added only every couple of months and only simple changes are made frequently), perform health checks once a month.
If your network is more dynamic (partitions or servers are added weekly or your organization is reorganizing), perform health checks weekly.
Factors that influence the timing of your health checks include the following:
- Number of partitions and replicas
- Stability of replica holding servers
- Amount of information in an eDirectory partition
- Object size and complexity
- Number of errors in previous DSRepairs
Identify Health Check Prerequisites
- Diagram your eDirectory Tree
- Diagram the Physical Layout of your network
- Determine your access to the tree
Review Health Check Elements
A complete health check includes all elements in the health check report and covers the following:
- eDirectory version
- Time synchronization
- Partition continuity
- Background processes
- Schema synchronization
- External references
- Limber status
Run the Agent Health Report
A 626 error lets you know that attempts to connect to the available server have failed.
A 625 error tells you that the communication process is not happening, most likely due to a LAN problem. These errors are not critical, but left unattended, they could cause multiple problems.
In this example, 694 is a Lost Entry, which indicates that the NDS object being updated using an NDS background process that has not been received.