119 lines
6.0 KiB
HTML
119 lines
6.0 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow"/>
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<title>Directory Server (LDAP) - Replication terminology</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="rzahyrepterm"></a>
|
||
|
|
<h3 id="rzahyrepterm">Replication terminology</h3>
|
||
|
|
<p>Some terminology used in describing replication:</p>
|
||
|
|
<dl>
|
||
|
|
<dt class="bold">Cascading replication</dt>
|
||
|
|
<dd>A replication topology in which there are multiple tiers of
|
||
|
|
servers. A peer/master server replicates to a set of read-only (forwarding)
|
||
|
|
servers which in turn replicate to other servers. Such a topology off-loads
|
||
|
|
replication work from the master servers.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Consumer server</dt>
|
||
|
|
<dd>A server which receives changes through replication from another
|
||
|
|
(supplier) server.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Credentials</dt>
|
||
|
|
<dd>Identify the method and required information that the supplier
|
||
|
|
uses in binding to the consumer. For simple binds, this includes the DN and
|
||
|
|
password. The credentials are stored in an entry the DN of which is specified
|
||
|
|
in the replication agreement.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Forwarding server</dt>
|
||
|
|
<dd>A read-only server that replicates all changes sent to it by a master
|
||
|
|
or peer. Client update requests are referred to the master or peer server.
|
||
|
|
</dd><img src="delta.gif" alt="Start of change" />
|
||
|
|
<dt class="bold">Gateway server</dt>
|
||
|
|
<dd>A server that forwards all replication traffic from the local replication
|
||
|
|
site where it resides to other gateway servers in the replicating network.
|
||
|
|
A gateway server receives replication traffic from other gateway servers within
|
||
|
|
the replication network, which it forwards to all servers on its local replication
|
||
|
|
site. Gateway servers must be masters (writable).
|
||
|
|
</dd><img src="deltaend.gif" alt="End of change" />
|
||
|
|
<dt class="bold">Master server</dt>
|
||
|
|
<dd>A server which is writable (can be updated) for a given subtree.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Nested subtree</dt>
|
||
|
|
<dd>A subtree within a replicated subtree of the directory.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Peer server</dt>
|
||
|
|
<dd>The term used for a master server when there are multiple masters for
|
||
|
|
a given subtree.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Replica group</dt>
|
||
|
|
<dd>The first entry created under a replication context has objectclass
|
||
|
|
ibm-replicaGroup and represents a collection of servers participating in replication.
|
||
|
|
It provides a convenient location to set ACL's to protect the replication
|
||
|
|
topology information. The administration tools currently support one replica
|
||
|
|
group under each replication context, named <span class="bold">ibm-replicagroup=default</span>.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Replica subentry</dt>
|
||
|
|
<dd>Below a replica group entry, one or more entries with objectclass ibm-replicaSubentry
|
||
|
|
can be created; one for each server participating in replication as a supplier.
|
||
|
|
The replica subentry identifies the role the server plays in replication:
|
||
|
|
master or read-only. A read-only server might, in turn, have replication agreements
|
||
|
|
to support cascading replication.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Replicated subtree</dt>
|
||
|
|
<dd>A portion of the DIT that is replicated from one server to another.
|
||
|
|
Under this design, a given subtree can be replicated to some servers and not
|
||
|
|
to others. A subtree can be writable on a given server, while other subtrees
|
||
|
|
might be read-only.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Replicating Network</dt>
|
||
|
|
<dd>A network that contains connected replication sites.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Replication agreement </dt>
|
||
|
|
<dd>Information contained in the directory that defines the 'connection'
|
||
|
|
or 'replication path' between two servers. One server is called the supplier
|
||
|
|
(the one that sends the changes) and the other is the consumer (the one that
|
||
|
|
receives the changes). The agreement contains all the information needed
|
||
|
|
for making a connection from the supplier to the consumer and scheduling replication.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Replication context</dt>
|
||
|
|
<dd>Identifies the root of a replicated subtree. The ibm-replicationContext
|
||
|
|
auxiliary object class can be added to an entry to mark it as the root of
|
||
|
|
a replicated area. The replication topology related information is maintained
|
||
|
|
in a set of entries created below a replication context.
|
||
|
|
</dd><img src="delta.gif" alt="Start of change" />
|
||
|
|
<dt class="bold">Replication site</dt>
|
||
|
|
<dd>A Gateway server and any master, peer, and replica servers configured
|
||
|
|
to replicate together.
|
||
|
|
</dd><img src="deltaend.gif" alt="End of change" />
|
||
|
|
<dt class="bold">Schedule</dt>
|
||
|
|
<dd>Replication can be scheduled to occur at particular times,
|
||
|
|
with changes on the supplier accumulated and sent in a batch. The replica
|
||
|
|
agreement contains the DN for the entry that supplies the schedule.
|
||
|
|
</dd>
|
||
|
|
<dt class="bold">Supplier server</dt>
|
||
|
|
<dd>A server which sends changes to another (consumer) server.
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|