You can migrate to Netscape Directory Server 4.1 or a later 4.x release from Netscape Directory Server 1.03, 1.04, or 3.x. When you migrate, you install the new Directory Server and then migrate your directory data from your old 3.x or earlier server to the new server. You can upgrade to a 4.1 or later 4.x server from a previous 4.x release. When you upgrade, you install directly over your currently installed 4.x server.
This chapter describes how in the following sections:
Upgrading a Single 4.x Directory Server
Migrating a Single Pre-4.0 Directory Server
Upgrading or Migrating a Replicated Site
Complete the following steps to upgrade your 4.x server:
"Step 1: Back Up Your Configuration and Database"
"Step 2: Upgrade the Server"
"Step 3: Upgrade the Schema"
http://home.netscape.com/eng/server/directory/4.1/relnotes.html#new
http://home.netscape.com/eng/server/directory/4.11/relnotes.html
Step 1: Back Up Your Configuration and Database
Before you upgrade your server, copy your configuration files to a safe place. The following files contain important configuration information:
slapd.conf
slapd.ldbm.conf
dsgw.conf—By default a copy of this file is located in each of the following directories:
<NSHOME>/admin-serv/config/dsgw.conf
<NSHOME>/dsgw/content/dsgw.conf
slapd.user_at.conf and slapd.user_oc.conf—By default, these files are located in <NSHOME>/slapd-<serverID>/config/
slapd.at.conf and slapd.oc.conf—If you directly modified these files in your old server, you will need a copy of each to manually upgrade your schema. If you did not directly modify these files, you do not need to create a backup. By default, these files are located in <NSHOME>/slapd-<serverID>/config/
Make a recent backup of your database.
Once you have backed up your critical configuration information, complete the following to upgrade a server:
Install a new 4.1 or later 4.x Directory Server as described in Chapter 2, "Using Express and Typical Install,", Chapter 3, "Using Custom Install," or Chapter 4, "Silent Installation." Also:
Make sure you choose to install the new server in the same directory where your old server is installed. By default this directory is /usr/netscape/server4/ on Unix, and C:\Netscape\Server4\ on Windows NT.
You will need to provide the old configuration directory administrator's ID and password during the upgrade.
Upgrade your schema as described in "Step 3: Upgrade the Schema".
When you upgrade to 4.1 or a later 4.x release, the upgrade process does not overwrite your old schema files. Instead, the new schema files are installed in the following directory:
<NSHOME>/bin/slapd/install/config/
Where <NSHOME> is the directory where you installed the new server.
Use the following table to decide which procedure you need to use to upgrade your schema:
Upgrading Standard Schema
If you did not modify the slapd.at.conf or slapd.oc.conf files in your old server, you can upgrade the schema as follows:
If you have not already done so, complete "Step 1: Back Up Your Configuration and Database" and "Step 2: Upgrade the Server".
Copy all the files in the following directory: <NSHOME>/bin/slapd/install/config/ except slapd.user_oc.conf and slapd.user_at.conf, to the directory where your 4.0 schema files are stored. By default this directory is: <NSHOME>/slapd-<ServerID>/config/
except slapd.user_oc.conf and slapd.user_at.conf, to the directory where your 4.0 schema files are stored. By default this directory is:
<NSHOME>/slapd-<ServerID>/config/
Restart the Directory Server.
If you modified the slapd.at.conf or slapd.oc.conf files in your old server, you need to do the following to upgrade your schema:
If you have not already done so, complete "Step 1: Back Up Your Configuration and Database" and "Step 2: Upgrade the Server". Make sure you create a backup copy of your schema files.
Copy all the files in the following directory: <NSHOME>/bin/slapd/install/config/ except slapd.user_oc.conf and slapd.user_at.conf, to the directory where your old 4.x schema files are stored. By default this directory is: <NSHOME>/slapd-<ServerID>/config/
except slapd.user_oc.conf and slapd.user_at.conf, to the directory where your old 4.x schema files are stored. By default this directory is:
Examine the copy you made during "Step 1: Back Up Your Configuration and Database" of the old 4.x slapd.at.conf and slapd.oc.conf files to discover all the schema additions that you made. If you added attributes to slapd.at.conf, you need to add them to the new Directory Server using the Directory Server Console. If you added new object classes to slapd.oc.conf, you need to add them to the new Directory Server using the Directory Server Console. If you added attributes to standard object classes in slapd.oc.conf, then you must do the following:
If you added attributes to slapd.at.conf, you need to add them to the new Directory Server using the Directory Server Console.
If you added new object classes to slapd.oc.conf, you need to add them to the new Directory Server using the Directory Server Console.
If you added attributes to standard object classes in slapd.oc.conf, then you must do the following:
Using the Directory Server Console, create a new object class that allows your custom attributes.
Place this new object class on every entry in your directory that uses the custom attributes.
See the Netscape Directory Server Administrator's Guide for information on adding object classes and attributes.
To migrate, complete these steps:
Read the information outlined in "Before You Migrate"
"Step 1: Back Up Configuration"
"Step 2: Migrate the Server"
If you modified your old slapd.at.conf or slapd.oc.conf files directly, you will also need to complete "Step 3: Migrate Custom Schema". Otherwise, the migration process automatically migrates schema.
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:
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.
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 Server 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.
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/relnotes.html#new http://home.netscape.com/eng/server/directory/4.1/relnotes.html#new http://home.netscape.com/eng/server/directory/4.11/relnotes.html
http://home.netscape.com/eng/server/directory/3.1/relnotes.html#new
http://home.netscape.com/eng/server/directory/4.0/relnotes.html#new
Before you migrate your server, copy your configuration files to a safe place. The following files contain important configuration information:
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.
Once you have backed up your configuration, complete the following to migrate a 1.03, 1.04, or 3.x server to 4.x:
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.
Shutdown your old Directory Server (this will automatically be done for you if the server is not shut down when you begin migration).
Start the Netscape Console using an account that has full read access to the server root.
In the Netscape Console's navigation tree, select the Server Group folder for the host on which the migration is occurring.
In the Object menu, select "Migrate Server Config...".
Enter the full path to the old server's installation root directory. For example: /usr/ns-home
/usr/ns-home
Select the old server to migrate from the resulting list.
Select Yes to overwrite any existing SIE data.
Select the new server to migrate the old directory data to. Select "Create New Instance" to create a new instance to hold the data.
Enter the Root DN password. This will be used for your Directory Server 4.x directory manager password. During migration, a window appears detailing problems the migration process encountered with custom schema and plugins. Where possible, this window also contains solutions to these problems. Make sure you take note of the information in this window.
During migration, a window appears detailing problems the migration process encountered with custom schema and plugins. Where possible, this window also contains solutions to these problems. Make sure you take note of the information in this window.
Step 3: Migrate Custom Schema
If you customized your old (3.x or earlier) 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:
Examine your old slapd.at.conf and slapd.oc.conf files to discover all the schema additions that you made there.
Place your custom schema elements in the following files: <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.
<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.
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.
Create a new object class that allows your 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.
Upgrade or migrate all your consumer servers first using the standard upgrade or migration process. See "Upgrading a Single 4.x Directory Server" or "Migrating a Single Pre-4.0 Directory Server" as appropriate.
Upgrade or migrate your supplier server.
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 that you 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.
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.
Previous
