Consumer Migration; Managing Console Fail Over - Netscape DIRECTORY SERVER 6.2 Installation Manual

Install Directory Server 6.x, registering against the first master's
2.
configuration instance.
Run the migration script following the instructions in "Migrating a Standalone
3.
Server" on page 92.
Once your hub is migrated, test replication and make sure that it is working
4.
correctly.
After you finish this process for the first hub, repeat the steps for any
5.
additional hubs.

Consumer Migration

To migrate a 5.x consumer server:
Stop the 5.x Directory Server.
1.
Install Directory Server 6.x, registering against the first master's
2.
configuration instance.
Run the migration script; see section "Migrating a Standalone Server" on
3.
page 92.
Once your consumer is migrated, test replication and make sure that it is
4.
working correctly.
After you finish this process for the first consumer, repeat the steps for any
5.
additional consumers.

Managing Console Fail Over

If you have a multi-master installation with
your two masters, 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:
Shut down the Administration Server and Directory Server.
1.
Change these files to reflect Server2's values:
2.
serverRoot/userdb/dbswitch.conf:directory default
ldap://configHostname:configPort/o%3DNetscapeRoot
serverRoot/admin-serv/config/adm.conf:ldapHost:
serverRoot/admin-serv/config/adm.conf:ldapPort:
o=NetscapeRoot
Chapter 6 Migrating and Upgrading From Previous Versions
Migration Procedure
replicated between
configHostname
configPort
105