Replication And Synchronization - Red Hat DIRECTORY SERVER 8.1 - DEPLOYMENT Deployment Manual

Hide thumbs Also See for DIRECTORY SERVER 8.1 - DEPLOYMENT:
Table of Contents

Advertisement

A consumer might contain replicated data from two suppliers, each with different schema. Whichever
supplier was updated last wins, and its schema is propagated to the consumer.
WARNING
Never update the schema on a consumer server, because the supplier server is unable
to resolve conflicts that occur, and replication fails. Schema should be maintained on a
supplier server in a replicated topology.
If the standard 99user.ldif file is used for custom schema, these changes are
replicated to all consumers. If there are custom schema files, ensure that these files are
copied to all servers after making changes on the supplier. After all of the files have been
copied, restart the server.
Section 3.4.7, "Creating Custom Schema Files"
See
The same Directory Server can hold read-write replicas for which it acts as a supplier and read-only
replicas for which it acts as a consumer. Therefore, always identify the server that will function as a
supplier for the schema, and then set up replication agreements between this supplier and all other
servers in the replication environment that will function as consumers for the schema information.
NOTE
Special replication agreements are not required to replicate the schema. If replication
has been configured between a supplier and a consumer, schema replication occurs by
default.
Changes made to custom schema files are only replicated if the schema is updated using
LDAP or the Directory Server Console. These custom schema files should be copied to
each server in order to maintain the information in the same schema file on all servers.
For more information, see
For more information on schema design, see

6.4.5. Replication and Synchronization

In order to propagate synchronized Windows entries throughout the Directory Server, use
synchronization within a multi-master environment. Synchronization agreement should be kept to the
lowest amount possible, preferably one per deployment. Multi-master replication allows the Windows
information to be available throughout the network, while limiting the data access point to a single
Directory Server.
Section 3.4.7, "Creating Custom Schema
Chapter 3, Designing the Directory
Replication and Synchronization
for more information.
Files".
Schema.
97

Advertisement

Table of Contents
loading

Table of Contents