Installation guide

Migration Prerequisites
90 Netscape Directory Server Installation Guide • December 2003
• Windows only. If you are migrating a Directory Server 5.x multi master
replicated (MMR) environment to Directory Server 6.2, before you run the
migration script, export all exports from the old server’s backend databases
using the
db2ldif -r option.
• When you run the migration script, it migrates the configuration files or
configuration entries, database instances, and schema with minimum manual
intervention. For complete information on the configuration parameters
and attributes that are migrated, check chapter “Migration from Earlier
Versions” of the Netscape Directory Server Configuration, Command, and File
Reference.
• Check the command syntax for the migration script in chapter
“Command-Line Scripts” of the 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.
While the migration will complete in this situation, you will probably find that you
cannot modify your data in Directory Server 6.x. Therefore, you are strongly
recommended to copy your custom schema into separate files before you
perform the migration. You can use the standard
slapd.user_oc.conf and
slapd.user_at.conf files or any files declared in slapd.conf with the useroc
and
userat keywords respectively. Make these changes with the server shut
down.
To separate your custom schema from your standard schema:
1. Examine your old slapd.at.conf and slapd.oc.conf files to discover all the
schema additions that you made there.
To ensure that you have properly identified all your changes to standard files,
you can compare them with the standard files provided in the
/bin/slapd/install/version4 directory. Alternatively, if you have already
tried to run the
migrateInstance6 script, use the notifications that it issues.