Novell EDIRECTORY 8.8 - GUIDE, Manual

Page: 55 / 574

Understanding Novell eDirectory 55
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
NOTE: Filtered replicas by default will have the Organization and the Organizational Unit as
mandatory filters.
For more information on setting up and managing filtered replicas, see Section 5.6, “Setting Up and
Managing Filtered Replicas,” on page 136 .
1.7 NetWare Bindery Emulation
Many applications, such as print servers and backup software, were written for NetWare versions
earlier than NetWare 4. These applications used the NetWare bindery instead of eDirectory for
network access and object manipulation.
The bindery is a flat database of objects such as Users, Groups, and Volumes known to a given
server. The bindery is server specific and server centric.
Older NetWare client software (such as the NETX bindery shell) used a bindery login procedure in
which a user logged in to a specific server only. Access to multiple servers required multiple logins
using multiple user accounts.
eDirectory allows applications written for a bindery to function using bindery services. Bindery
services allows you to set an eDirectory context or a number of contexts (up to 12) as an eDirectory
server’s virtual bindery. The context you set is called the server’s bindery context.
Following are some important facts about bindery services:
• To use bindery services, you must set a bindery context for the eDirectory server.
• Not all objects map to bindery objects. Many objects, such as Alias objects, do not have a
bindery equivalent.
• Most bindery applications have been upgraded to work with eDirectory. Check with your
application vendor to get the newest version.
• Each eDirectory server with a bindery context must hold a master or read/write replica of the
partition that includes the bindery context.
1.8 Server Synchronization in the Replica Ring
When multiple servers hold replicas of the same partition, those servers are considered a replica
ring. Synchronization is the propagation of directory information from one replica to another, so the
information in each partition is consistent with the other. eDirectory automatically keeps those
servers synchronized. For more information, refer
Section 3.4, “Synchronization,” on page 105
The following are the types of eDirectory synchronization:
• Normal Synchronization or Replica Synchronization
• Priority Sync
1.9 Access to Resources
eDirectory provides a basic level of network access security through default rights. You can provide
additional access control by completing the tasks outlined below.
• Assigning rights