56 Chapter 6. Migrating from Previous Versions6.3.4. Managing Console FailoverIf you have a multi-master installation with o=NetscapeRoot replicated between your two masters,server1 and server2, you can modify the Console on the second server (server2) so that it usesserver2’s instance instead of server1’s. (By default, writes with server2’s Console would bemade 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 defaultldap://configHostname:configPort/o%3DNetscapeRootserverRoot/admin-serv/config/adm.conf:ldapHost:configHostnameserverRoot/admin-serv/config/adm.conf:ldapPort:configPortserverRoot/shared/config/dbswitch.conf:directory defaultldap://configHostname:configPort/o%3DNetscapeRootserverRoot/slapd-serverID/config/dse.ldif:nsslapd-pluginarg0:ldap://configHostname:configPort/o%3DnetscapeRoot3. 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.ldifb. Locate the entry for the PTA plug-in:dn: cn=Pass Through Authentication,cn=plugins,cn=configc. Change nsslapd-pluginEnabled: on to nsslapd-pluginEnabled: off.d. Restart the Directory Server and Administration Server.6.4. Upgrading from Directory Server 7.x VersionsInstead of migrating the Directory Server, you can install an instance of Directory Server 7.1 on topof the Directory Server 7.0 by installing Directory Server 7.1 into the same server root directory. Thisupdates all the server files while preserving your entries and custom schema. These sections explainthe upgrade process:• Section 6.4.1 Before You Begin• Section 6.4.2 Upgrading• Section 6.4.3 After You Upgrade.