Ability to identify key configuration files that should be backed up before upgrading the Directory Server.
Dir 4.0b1 Installation Notes Server Installation Guide "Determine the Location of the Configuration Directory"
To avoid the need to perform manual schema migration in the future, never modify any schema files directly. Instead, use the schema editor in the Directory Server Console to add schema elements.
Factoid: Although the Server will run on systems with 32 MB of RAM, 64 MB is recommended.
| # Preparing To Upgrade This page describes the installation requirements for the Directory Server. To migrate to Netscape Directory Server 4.0, you must be running directory 1.03 or later. ### Background Before performing migration be aware that migration results in two instances of the directory server. One instance of the server is the configuration directory, that is, it contains all Netscape server registration information. The other server contains your migrated corporate data. The first directory server you install must be your configuration directory. Other requirements and suggestions for migration are: You must migrate using the same physical host; migration cannot occur over networked drives. Migration from 1.03 directory servers results in schema modifications (particularly schema deletions). You are advised to familiarize yourself with these schema changes. For details, see the Netscape Directory Server 3.0 release notes at: `http://home.netscape.com/eng/server/directory/3.0/relnotes.html#new` Your old schema files are backed up during the migration. Migration from 1.03 directory servers results in a conversion of your access control to a new format that was delivered in Directory 3.0. This conversion should occur with no difficulties, however you are advised to examine your access control after migration to ensure that it still works as expected. You are advised to familiarize yourself with features new in each release since you last installed your directory server. This information is available for each release in the following locations: `http://home.netscape.com/eng/server/directory/3.0/relnotes.html#new` `http://home.netscape.com/eng/server/directory/3.1/relnotes.html#new` `http://home.netscape.com/eng/server/directory/4.0/private1/beta_notes.htm#new` ### Migrating Custom Schema If you customized your old schema by modifying `slapd.at.conf` or `slapd.oc.conf` directly, then the server migration process will not migrate your custom schema for you. However, you will be 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 4.0 schema files in their place Your old schema is saved in nshome`/slapd-`servername`/migrate_config.` While the migration will complete in this situation, it may result in a directory that cannot be modified until you have straightened out your schema. Therefore, you are strongly recommended to separate your custom schema into files other than `slapd.oc.conf` and slapd.at.conf before you perform migration. 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. 2. Place your custom schema elements in the following files: nshome`/slapd-`servername`/config/slapd.user_at.conf` nshome`/slapd-`servername`/config/slapd.user_oc.conf` You should use these filenames because these are the names that the 3.x and 4.0 schema configuration editor write to. 3. Include these files into your `slapd.conf`file using the userat and useroc directives. Place your new directives at the same place in the file as where the other configuration files are included. The order in which the various configuration files are included is not important. Also, if you added attributes to standard object classes in `slapd.oc.conf`, then you must: 1. Create a new object class that allows your custom attributes. 2. Place this new object class on every entry in your directory that uses the custom attributes. ### Backing Up Your Files Before you migrate your server, copy your configuration files to a safe place. This includes: `slapd.conf` `dsgw.conf` `slapd.dynamic-ldbm.conf` (3.x servers only) `slapd.at.conf` and `slapd.oc.conf` (1.03 servers only) Custom schema files, if any. A recent backup of your database.

Copyright © 2000
Sun-Netscape Alliance