User Guide

24
000-0000-000
November 30, 2001
QuickStart Rev 99a
44
August 22, 2001
threads active on multiple processors. eDirectory itself is not processor-intensive, but it is I/O-intensive.
The following table illustrates typical system requirements for Novell eDirectory for Solaris.
Requirements for processors might be greater than the table indicates, depending upon additional services
available on the computer as well as the number of authentications, reads, and writes that the computer is
handling. Processes such as encryption and indexing can be processor-intensive.
FORCING THE BACKLINK PROCESS TO RUN
Because the internal eDirectory identifiers change when upgrading to Novell eDirectory, the backlink
process has to update backlinked objects for them to be consistent.
Backlinks keep track of external references to objects on other servers. For each external reference on a
server, the backlink process ensures that the real object exists in the correct location and verifies all backlink
attributes on the master of the replica. The backlink process occurs two hours after the database is open and
then every 780 minutes (13 hours). The interval is configurable from 2 minutes to 10,080 minutes (7 days).
After migrating to eDirectory, start the ndstrace process by issuing the ndstrace -l >log& command,
which runs the process at the background. You can force the backlink to run by issuing the ndstrace -c
SET DSTRACE=*B command from the ndstrace command prompt. You can then unload the ndstrace
process by issuing the ndstrace -u command. Running the backlink process is especially important on
servers that do not contain a replica.
Objects Processor Memory Hard Disk
100,000 Sun* Enterprise 220 384 MB 144 MB
1 million Sun Enterprise 450 2 GB 1.5 GB
10 million Sun Enterprise 4500 with multiple
processors
2 GB + 15 GB