Complete Contents
Introduction
Chapter 1 Preparing for Installation
Chapter 2 Using Express and Typical Install
Chapter 3 Using Custom Install
Chapter 4 Silent Installation
Chapter 5 Installing and Configuring the Synch Service
Chapter 6 Upgrading the Directory Server
Chapter 7 Troubleshooting
Previous Next Contents Index Bookshelf


Chapter 6 Upgrading the Directory Server

You can upgrade to Netscape Directory Server 4.x from Netscape Directory Server 1.03 or later. This chapter describes how in the following sections:


Migration Prerequisites
To migrate to Netscape Directory Server 4.x, you must be running directory 1.03 or later.

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.

For more information on the configuration directory, see "Determine the Location of the Configuration Directory".

Other requirements and suggestions for migration are:


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. 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 4.1 schema files in their place. Your old schema is saved in <NSHOME>/slapd-<serverID>/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:
  3. <NSHOME>/slapd-<serverID>/config/slapd.user_at.conf
    <NSHOME>/slapd-<serverID>/config/slapd.user_oc.conf

    You should use these filenames because these are the names that the 3.x and 4.x schema configuration editor write to.

  4. 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 do the following:

  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.

Note. 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.


Upgrading a Single Directory Server to Version 4.x
Before you migrate your server, copy your configuration files to a safe place. The following files contain important configuration information:

Once you have backed up your critical configuration information, do the following to migrate a server to 4.x:

  1. Install a new 4.x Directory Server as described in Chapter  2, "Using Express and Typical Install,", Chapter  3, "Using Custom Install," or Chapter  4, "Silent Installation." Do not use the same port number your production server uses (e.g. port 389) because this initial directory will be used for server registration purposes only.
  2. Shutdown your old Directory Server (this will automatically be done for you if the server is not shut down when you begin migration).
  3. Start the Netscape Console using an account that has full read access to the server root.
  4. In the Netscape Console's navigation tree, select the Server Group folder for the host on which the migration is occurring.
  5. In the Object menu, select "Migrate Server Config..."
  6. Enter the full path to the old server's installation root directory. For example:
  7. /usr/ns-home

  8. Select the old server to migrate from the resulting list.
  9. Select Yes to overwrite any existing SIE data.
  10. Select the new server to migrate the old directory data to. Select "Create New Instance" to create a new instance to hold the data.
  11. Enter the Root DN password. This will be used for your Directory Server 4.x directory manager password.
Your old server is then migrated. As a result of this migration, a new Directory Server 4.x server instance is installed using the configuration information obtained from your old Directory Server. In addition, the data from your old server is migrated to the new server and the new server is started.


Upgrading a Replicated Site
Instances of Directory Server 1.03 and 3.x can replicate to a 4.x directory. Therefore, to migrate a replicated site to 4.x, do the following:

  1. Migrate all your consumer servers first using the standard migration process.
  2. Once all consumer servers have been migrated, migrate your supplier server.
  3. If you are migrating a 1.03 supplier server, then you must configure the migrated server with a supplier DN password once the migration has been completed. Make sure you provide the same password as was configured for your 1.03 supplier server. For information on how to set a supplier DN password on a 4.x supplier server, see the Netscape Directory Server Administrator's Guide.
  4. If you are migrating a 1.03 supplier server, you must reinitialize all your consumer servers after the supplier has been migrated. Remember that for database sizes larger than 5000 entries, you should use offline consumer creation. For smaller databases, you can use online consumer creation. For information on how to initialize consumer servers, see the Netscape Directory Server Administrator's Guide.
 

© Copyright 1999 Netscape Communications Corporation