8. Migration

This page describes how the migration script works and walks you through a test migration from Netscape Directory Server 4.12 to iDS 5.0. It is divided into three sections.

1. Migration Overview
• Here we describe what the migration script will do.
2. Prerequisites
• Here we review what needs to be in place before performing the migration.
3. Migration Procedure
   • Here we we guide you step by step through a migration on your test system.

Migration Overview

The migration process is performed by simply running the migrateInstance5 script on the system where your previous version of the Directory Server is installed. The provided migration script can facilitate upgrading from Netscape Directory Server 4.0, 4.1, 4.11, or 4.12.

Q: What does the migration script [migrateInstance5] do? A: The migration script performs the following tasks in sequence:  Backs up your current configuration.  Checks the schema configuration files, and notifies you of any changes between the standard configuration files and the ones present on your system.  Creates a database for each suffix stored in the previous version of the Directory Server. (In Directory Server 5.0 you can have multiple databases, but just one suffix per database).  Migrates the server parameters and database parameters. (In Directory Server 5.0, these are stored in the directory itself).  Migrates user-defined schema objects.  Migrates indexes. Migrates standard server plug-ins.  Migrates the certificate database, and SSL parameters  Shuts down your previous version of the Directory Server before performing the migration process.

 

Prerequisites

This section lists the prerequisites that your system will need to meet before you can begin the migration process in the form of a checklist.

Migration Prerequisite Checklist

	Prerequisites
	1. You must be using Directory Server 4.0, 4.1, 4.11, or 4.12. When you run the migration script, the previous version of the server process ns-slapd should be stopped.
	2. Your previous version of the Directory Server and your new Directory Server 5.0 should be installed on the same host; migration should occur on local drives.
	3. When you install iPlanet Directory Server 5.0, you must choose different ports for secured LDAP connections.
	4. Your iPlanet Directory Server 5.0 must be running when you execute the migration script.

Q:What prerequisites apply when I perform migration on my production system? A: All of the prerequisites listed above apply. In addition, there are two additional prerequisites: 1. Any custom schema that you created in your previous version of the Directory Server must be stored in the slapd.user_oc.conf and slapd.user_at.conf files. If it is not, refer to the procedure described in Identifying Custom Schema to move it to those files. 2. Set the following environment variables:  PERL5LIB=server5root$/bin$/slapd$/admin$/bin  PATH=server5root$/bin$/slapd$/admin$/bin where server5root represents the directory under which you installed the Directory Server.

 

Migration Procedure

Now we are going to practice migrating a previous version of the server to iDS 5.0. In this exercise, we will assume that you have followed the installation instructions up until now and still have Directory Server 5.0 running on your test system. You will want to follow these procedures as root user.

Step 1: Start with a clean test system

If you still have iDS 5.0 running and installed, now is a time to uninstall. Navigate to your iDS 5.0 root and type in the uninstall command as shown in the example above.

#cd /train/iplanet/servers # ./uninstall

Following uninstallion you may still have remaining files. Navigate to one level above your root directory and use rm -rf to remove that directory and its subdirectories. You can use ls to confirm that all the files have been removed.

#cd /train #ls   iplanet # rm -rf iplanet #ls

Step 2: Install Directory Server 4.12

Directory Server 4.12 will act as your previous version of the server. To install Directory Server 4,12, we recommend following the instructions for installing Directory Server 5.0 found in this training with the following modifications.

1. Choose the 4.12 version from the iPlanet Test Drive Site.

2. Save it in a file separate from where the iDS 5.0 will be. We recommend saving the Netscape Directory Server 4.12 in a directory called temp1 outside of the previous directory but still in train.

3. Install your 4.12 Server into the temp1 directory you created.

Install location [/usr/netscape/server4]:/temp1/netscape/server4

4. Choose the default ports.

Q: Why choose the same ports? A: By continuing to use the same ports for the previous version of the server and for iDS 5.0 (port 389 for the Directory Server and port 4000 for the Administrative Server) you can ensure that the applications pointing to the previous version of the server will now point to your new server. For the directory server- Directory server network port [389]:389 For the administrative server- Administrative server network port [13294]:4000

Step 3: Stop your previous version of the Directory Server.

Navigate to the root folder of your 4.12 Directory Server and stop the slapd process. Note that if you do not stop it, the migration script does it for you.

# cd /train/temp1/netscape/server4/slapd-arius # ./stop-slapd

Also, stop the admininstrative server by navigating to the server root directory and typing ./stop-admin.

# cd /train//temp1/netscape/server4/ # ./stop-admin

 

Q: How can I confirm that my server stopped? A: Type the stop command again. This time it should tell you that the server has already stopped as shown below. For the directory server- # ./stop-slapd server not running For the administrative server- # ./stop-admin server not running

Step 4: Install a new 5.0 Directory Server

The installation process is outlined in Installing the Software. You can begin by running the ./setup command on the software you still have in your /train directory.

Step 5: Run the migration script

Navigate to
/train/iplanet/servers/bin/slapd/admin/bin ,
then enter the following command:
migrateInstance5 -D rootDN -w passwd -p port -o server4ID -n server5ID [-h host]

where:

rootDN= "cn=Directory Manager"
DN for Directory Manager in Directory Server 5.0

passwd = dirmanager
password for Directory Manager in Directory Server 5.0

port = 389
LDAP port number in Directory Server 5.0

server4ID= /train/temp1/netscape/server4/slapd-<serverID>
path to the previous version of the Directory Server directory

server5ID = /train/iplanet/servers/slapd-<serverID>
path to the Directory Server 5.0 directory

host=
name of the machine on which the migration is performed (localhost by default)

# cd /usr/iplanet/servers/bin/slapd/admin/bin # ./migrateInstance5 -D "cn=Directory Manager" -w dirmanager -p 389 -o /train/temp1/netscape/server4/slapd-arius -n /train/iplanet/servers/slapd-arius

Note: ./migrateInstance5...appears all on one line.

Q: What can I do if I forget my Directory manager DN or password? A: You can find out what the Directory Manager DN is by examining train/iplanet/servers/slapd-<server ID>/config/dse.ldif and looking for the rootdn parameter. In our example it is located in this path: /train/iplanet/servers/slapd-arius/config/dse.ldif By design the password is not stored in plain text. You will need to reset a new one. To reset your pathword follow the instructions in Common Installation Problems.

Step 6: Provide a path and filename for your backup directory

Accept the default path and filename for your backup directory.

Connected to 5.0 LDAP server Backup /train/iplanet/servers/slapd-arius/config on /train/iplanet/servers/slapd-arius/config_backup ... Where do you want to back up your configuration directory [/train/iplanet/servers/slapd-arius/config_backup] ?

The following is an extract of the script's output:

Parse the configuration file: /train/temp1/netscape/server4/slapd-arius/config /slapd.conf... Suffix o=mcom.com doesn't exist Backend: MigratedDB_0 has been created !!! Suffix dc=arius,dc=mcom,dc=com doesn't exist Backend: MigratedDB_1 has been created !!! For the suffix o=NetscapeRoot, we do nothing Migrate key/cert databases... Update general server parameters... Update successfully nsslapd-reservedescriptors Update successfully passwordHistory Update successfully nsslapd-errorlog-maxlogsperdir Update successfully nsslapd-enquote-sup-oc Update successfully passwordStorageScheme Update successfully nsslapd-rootpwstoragescheme Update global LDBM parameters... Update successfully nsslapd-mode Update specific backend parameters... Migrate DSE entries... Migrate attributes... Migrate objectclasses... Migrate indexes... Migrate plugin's... Shutting down server slapd-arius . . . . . . data processing... Processing... . . .

Step 7:Your previous version of the Directory Server is migrated

As a result of this migration, a new Directory Server 5.0 instance is installed using the configuration information obtained from your previous version of the Directory Server. In addition, the data from your old server is migrated to the new server and the new server is started.

You should receive a message like the one below.

****** End of migration ****** -> Migration started at Tue Mar 6 23:11:42 2001 -> Migration ended at Tue Mar 6 23:13:00 2001

Summary

In this section we walked through the migration process. First we uninstalled iDS 5.0 for a clean start. Then we installed a previous version of iPlanet Directory Server. Finally we migrated this previous version of Directory Server to the latest 5.0 version.