NetWare 4.1/9000 Concepts

1-112
NetWare Glossary
N
Replicas
For NetWare Directory Services to be distributed across a network, the
database must be stored on many servers. Rather than have a copy of the
whole database on each server, replicas of each partition are stored on many
servers throughout the network.
A replica is a copy of a partition. You can create an unlimited number of
replicas for each partition and store them on any server in the network.
Replicas serve two purposes:
• To eliminate any single point of failure.
For example, if a disk crashes or a server goes down, a replica on a server in
another location can still authenticate users to the network and provide
information on objects in that partition.
• To provide faster access to information for users across a WAN link.
For example, if users must use a WAN link to access information, decrease
access time and network traffic by placing a replica containing the needed
information on a server that users can access locally.
See also: “Replica.”
Bindery compatibility
To provide compatibility with bindery-based versions of NetWare that may
co-exist with NetWare Directory Services on the network, NetWare 4
features bindery services.
Objects in a bindery exist in a flat database instead of a hierarchical database
like a Directory tree. Bindery services occur when NetWare Directory
Services provides a flat structure for the objects within an Organization or
Organizational Unit container object.
All objects within that container object can then be accessed both by
NetWare Directory Services objects and by bindery-based clients and
servers. Bindery services apply only to leaf objects in that Organizational
Unit.
The Organizational Unit where bindery services are set is called the bindery
context. You can change the bindery context by using the graphical
“NetWare Setup” or the command line “nwcm” utility.