Table of Contents
Advertisement
A C C O U N T M A N A G E M E N T
NDS scales well on a single processor. However, NDS 8.5 takes advantage of multiple
processors. Adding processors improves performance in some areas, for example, logins
and having multiple threads active on multiple processors. NDS itself is not processor-
intensive, but it is I/O-intensive.
The following table illustrates typical system requirements for NDS eDirectory for Tru64
UNIX:
Objects
100,000
1 million
10 million
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 NDS identifiers change when upgrading to NDS 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 NDS, we recommend that you force the backlink to run by issuing a
SET DSTRACE=*B command from the ndstrace command prompt. Running the backlink
process is especially important on servers that do not contain a replica.
Prerequisites
NDS Server must be installed on all servers that you want to place a NDS replica on.
" Meet the platform specific "System Requirements" on page 35.
Processor
Alpha 64-bit processor
Alpha 64-bit processor
Alpha 64-bit processor
36
Memory
Hard Disk
384 MB
144 MB
2 GB
1.5 GB
2 GB +
15 GB
Advertisement
Table of Contents
