Netscape NETSCAPE DIRECTORY SERVER 6.02, Руководство по установке

Страница: 61 / 96

Identifying Custom Schema
Chapter 6 Migrating From Previous Versions 61
• 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” to move it to those files.
• Any custom schema that you created in a 5.0 Directory Server must be stored
in an LDIF file in the
/usr/netscape/servers/slapd-
serverID
/config/schema
directory.
• The migration script does not migrate any data from Directory Server 4.x to
6.02 if both have the same suffix name. To ensure data migration, install your
new Directory Server with some dummy suffix names.
• On UNIX, set the following environment variables:
PERL5LIB=/usr/netscape/servers/bin/slapd/admin/bin
PATH=/usr/netscape/servers/bin/slapd/admin/bin:$PATH
In all cases, replace serverroot with the path to you installation directory.
• Be sure to read the migration-related information in chapters “Migration from
Earlier Versions” and “Command-Line Scripts” of Netscape Directory Server
Configuration, Command, and File Reference.
Identifying Custom Schema
If you customized the schema in your legacy Directory Server by modifying
slapd.at.conf
or
slapd.oc.conf
directly, then the server migration process
cannot migrate your custom schema for you. Instead, you are notified during
migration that you have modified the standard schema and that you need to
manually fix the problem. The migration process then saves a copy of your schema
files and uses standard legacy schema files in their place.