ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahy_5.4.0.1/rzahyrepmig.htm

107 lines
7.4 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) - Migrating a network of replicating servers</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="rzahyrepmig"></a>
<h3 id="rzahyrepmig">Migrating a network of replicating servers</h3>
<p>The first time that the master server is started, it migrates the information
in the directory that controls replication. The entries with objectclass replicaObject
under cn=localhost are replaced with entries used by the new replication model
(for more information, see <a href="rzahyreplication-c.htm#rzahyreplication-c">Replication</a>). The master
server is configured to replicate all the suffixes in the directory. The agreement
entries are created with the attribute ibm-replicationOnHold set to true.
This allows updates made to the master to be accumulated for the replica until
the replica is ready.</p>
<p>These entries are referred to as the replication topology. The new master
can be used with replicas running prior versions; data related to the new
functions will not be replicated to the back-level servers. It is necessary
to export the replication topology entries from the master and add them to
each replica after the replica server has been migrated. To export the entries,
use the Qshell command line tool <a href="rzahyldapsrch.htm#rzahyldapsrch">ldapsearch</a> and save the
output to a file. The search command is similar to the following:</p>
<pre class="xmp">ldapsearch -h <span class="italic">master-server-host-name</span> -p <span class="italic">master-server-port</span> \
-D <span class="italic">master-server-admin-DN</span> -w <span class="italic">master-server-admin-password</span> \
-b ibm-replicagroup=default,<span class="italic">suffix-entry-DN</span> \
-L "(|(objectclass=ibm-replicaSubEntry)(objectclass=ibm-replicationAgreement))" \
> replication.topology.ldif</pre>
<p>This command creates an output LDIF file named replication.topology.ldif
in the current working directory. The file contains only the new entries. </p>
<a name="wq83"></a>
<div class="notetitle" id="wq83">Note:</div>
<div class="notebody">Do not include the following suffixes:
<ul>
<li>cn=changelog</li>
<li>cn=localhost</li>
<li>cn=pwdpolicy</li>
<li>cn=schema</li>
<li>cn=configuration</li></ul>Include only user-created suffixes.</div>
<p>Repeat the command for each suffix entry on the master, but replace &quot;>&quot;
with &quot;>>&quot; to append the data to the output file for subsequent searches.
After the file is complete, copy it to the replica servers.</p>
<p>Add the file to the replica servers after they have been successfully migrated;
do not add the file to servers running previous versions of the directory
server. You must start and stop the server before you add the file.</p>
<p>To start the server, use the <span class="bold">Start</span> option in iSeries
Navigator. For more information, see<a href="rzahysta-pi.htm#rzahysta-pi">Start/stop the Directory Server</a>.</p>
<p>To stop the server, use the <span class="bold">Stop</span> option in iSeries
Navigator. For more information, see <a href="rzahysta-pi.htm#rzahysta-pi">Start/stop the Directory Server</a>.</p>
<p>When you add the file to a replica server, be sure that the replica server
is not started. To add the data, use the <span class="bold">Import File</span> option
in iSeries Navigator.</p>
<p>After the replication topology entries are loaded, start the replica server
and resume replication. You can resume replication in one of the following
ways: </p>
<ul>
<li>On the master server, use <span class="bold">Manage Queues in Replication
Management</span> in the Web administration tool.</li>
<li>Use the <span class="bold">ldapexop</span> command line utility. For example:
<pre class="xmp">ldapexop -h <span class="italic">master-server-host-name</span> -p <span class="italic">master-server-port</span> \
-D <span class="italic">master-server-admin-DN</span> -w <span class="italic">master-server-admin-password</span> \
-op controlrepl -action resume -ra <span class="italic">replica-agreement-DN</span></pre>This command resumes replication for the server defined in the
entry with the specified DN.</li></ul>
<p>To determine which replica agreement DN corresponds to a replica server,
look in the replication.topology.ldif file. The master server will log a
message that replication has started for that replica and a warning that the
replica server's ID in the agreement does not match the replica's server ID.
To update the replica agreement to use the correct server ID, use <span class="bold">Replication Management</span> in the Web administration tool, or the command
line tool <span class="bold">ldapmodify</span>. For example:</p>
<pre class="xmp">ldapmodify -c -h <span class="italic">master-server-host-name</span> -p <span class="italic">master-server-port</span> \
-D <span class="italic">master-server-admin-DN</span> -w <span class="italic">master-server-admin-password</span>
dn: <span class="italic">replica-agreement-DN</span>
changetype: modify
replace: ibm-replicaConsumerID
ibm-replicaConsumerID: <span class="italic">replica-server-ID</span>
</pre><p class="indatacontent">You can enter these commands directly on the command line, or you can
save the commands in an LDIF file and supply them to the command with the <span class="bold">-i <span class="italic">file</span></span> option.
Use <span class="bold">End Previous Request</span> to stop the command.</p>
<p>Migration for this replica is complete.</p>
<p>To continue to use a replica running a previous version, it is still necessary
to resume replication using the command line tool <span class="bold">ldapexop</span> or <span class="bold">Replication Management</span> in the Web
administration tool for that replica. If a replica running a previous version
is migrated later, use the command line tool <span class="bold">ldapdiff</span> to synchronize the directory data. This will ensure that entries or
attributes that were not replicated are updated on the replica.</p>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>