(NDS) A relational database that is distributed across your entire network. NDS provides you with global access to all network resources to which you have been given rights, regardless of where they are physically located.
NDS treats all network resources as objects in a distributed database known as the Novell Directory database, also referred to as the Directory.
All users log in to a multiserver network and view the entire network as a single information system. This single view provides for increased productivity and reduced administrative costs.
NOTE: NDS helps you manage Directory resources such as NetWare servers and volumes, but it doesn't provide control over the file system (files and file directories). Graphical and text utilities are available that help you control the file system.
When a user accesses resources on the network, background authentication processes verify that the user has rights to use those resources. Authentication allows users (who have logged in) to access any server, volume, or printer to which they have rights. User trustee rights restrict the user's access within the network. (See also Authentication; Login scripts; Rights; Trustee.) Within NDS, objects represent network resources. An object consists of categories of information, called properties, and the data in those properties. The information is stored in the Novell Directory database. Some objects represent physical entities. For example, a User object represents a user and a Printer object represents a printer. Some objects represent logical entities, such as groups and print queues. Other objects, such as the Organizational Unit object, help you organize and manage objects. (See Object.) NDS operates in a logical organization called the Directory tree. It is called a Directory tree because objects are stored in a hierarchical tree structure, starting with a root object and branching out. (See Directory tree.) To make it more manageable, the Novell Directory database is divided into smaller portions called Directory partitions. Directory partitions are created by default when you install NetWare 4 on a server in a new context in the Directory tree. (See Novell Directory partition.) For NDS to be distributed across a network, the Directory database must be stored on many servers. Rather than have a copy of the whole Directory database on each server, Directory replicas of each Directory partition are stored on many servers throughout the network. Directory partition replication improves access and provides the Directory with fault tolerance. Since a Directory partition can be replicated at several locations, damage to one of the Directory replicas doesn't need to interrupt access to the Directory partition information. (See Novell Directory replica.) Time synchronization establishes the order of events in NDS. Whenever an event occurs in the Directory, such as a password changed or an object renamed, NDS requests a time stamp so that the Directory replicas are updated in the correct order. (See Time synchronization.) NDS replaces the bindery, which served as the system database in earlier versions of NetWare. To provide compatibility with earlier, bindery-based versions of NetWare that may co-exist with NDS on the network, NetWare 4 features bindery services. (See Bindery services.)Authentication
Objects
The Directory Tree
Directory Partitions
Directory Replicas
Time Synchronization
Bindery Compatibility