Solving Common Replication Conflicts - Netscape DIRECTORY SERVER 6.1 - ADMINISTRATOR Administrator's Manual

Solving Common Replication Conflicts

In the "Configuration file" field, type the path to the configuration file you
6.
created in Step 1 and click OK.
The replication-status page appears; by default, the page gets refreshed every
300 seconds.
Solving Common Replication Conflicts
Multi-master replication uses a loose consistency replication model. This means
that the same entries can be changed on different servers. When replication occurs
between the two servers, the conflicting changes need to be resolved. Mostly,
resolution occurs automatically, based on the timestamp associated with the
change on each server. The most recent change takes precedence.
However, there are some cases where change conflicts require manual intervention
in order to reach a resolution. Entries that have a change conflict that cannot be
resolved automatically by the replication process, contain a conflict marker
attribute
attribute which makes it simple to search for entries that contain this attribute.
For example, you could use the following
prompt% ldapsearch -D adminDN -w passwd -b "dc=example,dc=com"
"nsds5ReplConflict=*"
For performance reasons, if you find that you have many conflicting entries every
day, you may want to index the
indexing, refer to Chapter 10, "Managing Indexes."
This section contains the procedures for the following conflict resolution
procedures:
• Solving Naming Conflicts
• Solving Orphan Entry Conflicts
• Solving Potential Interoperability Problems
330 Netscape Directory Server Administrator's Guide • August 2002
nsds5ReplConflict
. The
nsdsReplConflict
ldapsearch
nsds5ReplConflict
attribute is an operational
command:
attribute. For information on