Installation guide

Migration Procedure
Chapter 6 Migrating from Previous Versions 87
Managing Console Failover
If you have a multi-master installation with o=NetscapeRoot replicated between
your two suppliers, server1 and server2, you can modify the Console on the second
server (server2) so that it uses server2’s instance instead of server1’s. (By default,
writes with server2’s Console would be made to server1 then replicated over.)
To accomplish this, you must:
1. Shut down the Administration Server and Directory Server.
2. Change these files to reflect server2’s values:
serverRoot/userdb/dbswitch.conf:directory default
ldap://configHostname:configPort/o%3DNetscapeRoot
serverRoot/admin-serv/config/adm.conf:ldapHost:configHostname
serverRoot/admin-serv/config/adm.conf:ldapPort:configPort
serverRoot/shared/config/dbswitch.conf:directory default
ldap://configHostname:configPort/o%3DNetscapeRoot
serverRoot/slapd-serverID/config/dse.ldif:nsslapd-pluginarg0:
ldap://configHostname:configPort/o%3DnetscapeRoot
3.
Turn off the Pass-through Authentication (PTA) Plug-in on server2 by editing
its
dse.ldif file.
a. In a text editor, open this file:
serverRoot/slapd-serverID/config/dse.ldif
b. Locate the entry for the PTA plug-in:
dn: cn=Pass Through Authentication,cn=plugins,cn=config
c. Change nsslapd-pluginEnabled: on to nsslapd-pluginEnabled: off.
4. Restart the Directory Server and Administration Server.
Migrating Windows
The process of migrating Directory Server on Windows is slightly different than on
UNIX platforms. The following sections describe how to migrate a standalone
Windows Directory Server and Windows in a multi-master environment.
install.book Page 87 Wednesday, November 24, 2004 11:30 AM