Installation guide
Migration Prerequisites
Chapter 6 Migrating and Upgrading From Previous Versions 89
• Do not install the new Directory Server on top of an existing Directory
Server installation. Install your new Directory Server in a separate directory.
Migrate your legacy directory data into your new directory and when you
are satisfied with the result of the migration, remove your legacy Directory
Server.
• If you want to continue to run your legacy Directory Server, when you
install the new Directory Server choose different ports for LDAP traffic and
for secured connections from the ones used by your legacy Directory
Server.
If you will not be running your legacy Directory Server, use the same port
numbers to ensure that any directory clients that have static configuration
information (including Directory Server port numbers) will continue to
work.
• Your new Directory Server must be running when you execute the
migration script.
• Any custom schema that you created in a legacy 4.x Directory Server must
be stored in the default files or included using an include statement in the
slapd.conf file. The default files for custom schema are slapd.user_oc.conf
and
slapd.user_at.conf files in Directory Server 4.x. If you have
custom schema that is not stored in those files, refer to the procedure
described in “Identifying Custom Schema” on page 90” to move it to those
files.
• Any custom schema that you created in a 5.x Directory Server must be
stored in an LDIF file in the
serverRoot/slapd-serverID/config/schema
directory.
• Before performing the migration, check that the user-defined variables contain
the following associated values, where server6Root is the path to where your
new, Directory Server 6.x is installed:
On UNIX, set the following environment variables:
PERL5LIB=server6Root/bin/slapd/admin/bin
PATH=server6Root/bin/slapd/admin/bin:$PATH
On Windows, set the following environment variables:
PERL5LIB=server6Root\bin\slapd\admin\bin
PATH=server6Root\bin\slapd\admin\bin