1. Stop your legacy Directory Server.
   
   If you do not stop the legacy Directory Server, the migration script does it for you.
   
   
2. On the machine where your legacy Directory Server is installed, install a new 7.x Directory Server.
   
   The installation process is described in chapter 2, "Using Express and Typical Installation," or chapter 4, "Silent Installation and Instance Creation."
   
   Use the same port numbers as your legacy production server if you want to ensure that any directory clients that have static configuration information (including Directory Server port numbers) will continue to work.
   
   
3. Run the migration script.
   
   As root user (on UNIX) or administrator (on Windows), change directory to serverRoot/bin/slapd/admin/bin. Then enter the following command:
   
   On UNIX:
   
   migrateInstance7 -D rootDN -w password -p port -o oldInstancePath -n newInstancePath
   
   On Windows (see also Migrating Windows):
   
   perl migrateInstance7 -D rootDN -w password -p port -o oldInstancePath -n newInstancePath -d "oldDataDirectoryPath"
   
   where:
   
   
   • rootDN is the Directory Server 7.x user DN with root permissions, such as Directory Manager.
     
     
   • password is the password for Directory Manager in Directory Server 7.x.
     
     
   • port is the LDAP port number assigned to Directory Server 7.x.
   
   
   • oldInstancePath is the path to the installation directory of the legacy Directory Server (for example, /usr/netscape/server6/slapd-serverID).
   
   
   • newInstancePath is the path to the installation directory of Directory Server 7.x (for example, /usr/netscape/servers/slapd-serverID).
     
     
   • oldDataDirectoryPath is the path to the stored directory data from the legacy installation (for example, c:\data).
     
   
   The following is an example of a command you would use on a UNIX machine to migrate an instance of Directory Server 6.11 to Directory Server 7.0:
   
   migrateInstance7 -D "cn=Directory Manager" -w secret -p 389
   -o /usr/netscape/server611/slapd-phonebook
   -n /usr/netscape/servers/slapd-phonebook
   
   The following is an example of the same command on a Windows machine:
   
   perl migrateInstance7 -D "cn=Directory Manager" -w secret -p 389
   -o c:\ds621\servers\slapd-phonebook
   -n c:\netscape\servers\slapd-phonebook
   -d "c:\data"
   
   
4. Follow the prompts. For example, if you're prompted to provide a path and filename for your backup directory, enter one or accept the default.
   
   The migration process starts. At the end of migration, your legacy Directory Server is migrated. Additionally, as a result of this migration, a new Directory Server 7.x instance is installed using the configuration information obtained from your legacy Directory Server; the data from your old server is migrated to the new server; and the new server is started.
   
   A sample output showing migration of Directory Server 6.11 to Directory Server 7.0 is provided below. Notice that the script detects three backends, backend1, backend2, and userRoot, which exist in the legacy server as well as in the new server instances. To demonstrate the various options, for each backend a different option was chosen: for backend1, the choice was to continue with the migration and export processes; for backend2, the choice was to continue with the migration process only (without exporting); and, for userRoot, the choice was to skip the migration process.

migrate6to7 -D "cn=directory manager" -w secret12 -p 11440 -o
/export/home/jdoe/611-latest/slapd-bart -n
/export/home/jdoe/70-latest/slapd-bart -t 3 -L log.out

oldDir: /export/home/jdoe/611-latest,
oldHome:/export/home/jdoe/611-latest/slapd-bart,
oldConfDir: /export/home/jdoe/611-latest/slapd-bart/config/,
ldif_rep: /export/home/jdoe/611-latest/slapd-bart/config//ldif/,

rootDN: cn=directory manager,
Port: 11440,
Newname: bart

Shutdown the legacy Directory Server instance:
/usr/netscape/servers/ds611/slapd-bart

Shutting down server slapd-bart . . .

. . .

Name of the old LDAP server: bart.netscape.com
Name of the new LDAP server: bart.netscape.com
6.11 localuser: jdoe, uid: 9871, gid: 10
7.0 localuser: jdoe, uid: 9871, gid: 10

Backup /export/home/jdoe/70-latest/slapd-bart/config on /export/home/jdoe/70-latest/slapd-bart/config_backup ...

Where do you want to back up your configuration directory
[/export/home/jdoe/70-latest/slapd-bart/config_backup] ?

Migrate the schema...

Connected to 7.0 LDAP server

-------------------------------------------------------------------------

Parse the old DSE ldif file:
/export/home/jdoe/611-latest/slapd-bart/config/dse.ldif *****

This may take a while ...

 

Migrate DSE entries...

SECURITY - Update successfull: cn=encryption,cn=config
SNMP - Update successfull: cn=snmp,cn=config

Compared to the old instance, the current new plugin cn=referential
integrity postoperation,cn=plugins,cn=config belongs this attribute:
nsslapd-pluginarg7

Param: nstransmittedcontrols values To migrate: 2.16.840.1.113730.3.4.2
2.16.840.1.113730.3.4.9 1.2.840.113556.1.4.473 1.3.6.1.4.1.1466.29539.12
Param: nstransmittedcontrols new current values: 2.16.840.1.113730.3.4.2
2.16.840.1.113730.3.4.9 1.2.840.113556.1.4.473 1.3.6.1.4.1.1466.29539.12
Param: nsslapd-timelimit values To migrate: 3600
Param: nsslapd-timelimit new current values: 3600
Param: nsconcurrentbindlimit values To migrate: 10
Param: nsconcurrentbindlimit new current values: 10
Param: nsbindconnectionslimit values To migrate: 3
Param: nsbindconnectionslimit new current values: 3
Param: nsconnectionlife values To migrate: 0
Param: nsconnectionlife new current values: 0
Param: nsbindretrylimit values To migrate: 3
Param: nsbindretrylimit new current values: 3
Param: nsoperationconnectionslimit values To migrate: 10
Param: nsoperationconnectionslimit new current values: 10
Param: nsreferralonscopedsearch values To migrate: off
Param: nsreferralonscopedsearch new current values: off
Param: nsmaxtestresponsedelay values To migrate: 15
Param: nsmaxtestresponsedelay new current values: 15
Param: nsmaxresponsedelay values To migrate: 60
Param: nsmaxresponsedelay new current values: 60
Param: nsbindtimeout values To migrate: 15
Param: nsbindtimeout new current values: 15
Param: nsabandonedsearchcheckinterval values To migrate: 2
Param: nsabandonedsearchcheckinterval new current values: 2
Param: nsconcurrentoperationslimit values To migrate: 10
Param: nsconcurrentoperationslimit new current values: 10
Param: nschecklocalaci values To migrate: off
Param: nschecklocalaci new current values: off
Param: nshoplimit values To migrate: 10
Param: nshoplimit new current values: 10
Param: nsslapd-sizelimit values To migrate: 2000
Param: nsslapd-sizelimit new current values: 2000
Param: nsproxiedauthorization values To migrate: on
Param: nsproxiedauthorization new current values: on

-------------------------------------------------------------------------

Migrate LDBM backend instances...

 

*** LDBM_BACKEND_INSTANCE - cn=backend1,cn=ldbm database,cn=plugins,cn=config already exists

*** Migration will overwrite existing database
Do you want to continue Yes/No [No] ? y
Do you want to export the existing data Yes/No [Yes] ?

Enter the full pathname of the file
[/export/home/jdoe/70-latest/slapd-bart/db_backup/backend1.ldif]:

Existing data will be exported under
/export/home/jdoe/70-latest/slapd-bart/db_backup/backend1.ldif

Continue Yes/No [No] ? y

Now backing up database backend1 in
/export/home/jdoe/70-latest/slapd-bart/db_backup/backend1.ldif

Shutting down server slapd-bart . . .

ldiffile: /export/home/jdoe/70-latest/slapd-bart/db_backup/backend1.ldif
[12/Jun/2002:10:32:05 -0700] - export backend1: Processed 3 entries (100%).
[12/Jun/2002:10:32:05 -0700] - Waiting for 4 database threads to stop
[12/Jun/2002:10:32:07 -0700] - All database threads now stopped

try to reconnect to search cn=backend2,cn=ldbm database,cn=plugins,cn=config

*** LDBM_BACKEND_INSTANCE - cn=backend2,cn=ldbm database,cn=plugins,cn=config already exists

*** Migration will overwrite existing database

Do you want to continue Yes/No [No] ? y
Do you want to export the existing data Yes/No [Yes] ? n

We should add the backend instance cn=backend3,cn=ldbm database,cn=plugins,cn=config

LDBM_BACKEND_INSTANCE - Add successfull: cn=backend3,cn=ldbm database,cn=plugins,cn=config

 

*** INFORMATION - NetscapeRoot is NOT migrated

 

*** LDBM_BACKEND_INSTANCE - cn=userroot,cn=ldbm database,cn=plugins,cn=config already exists

*** Migration will overwrite existing database

Do you want to continue Yes/No [No] ?

*** Migration will not update it

-------------------------------------------------------------------------

Migrate mapping tree...

*** MAPPING_TREE - cn="dc=backend1,dc=com",cn=mapping tree,cn=config already exists
*** Migration will not add the suffix
*** MAPPING_TREE - cn="dc=backend2,dc=com",cn=mapping tree,cn=config already exists
*** Migration will not add the suffix

MAPPING_TREE - Add successfull: cn="dc=backend3,dc=com",cn=mapping tree,cn=config
*** MAPPING_TREE - cn="dc=netscape,dc=com",cn=mapping tree,cn=config already exists
*** Migration will not add the suffix

-------------------------------------------------------------------------

Migrate default indexes...

-------------------------------------------------------------------------

Migrate indexes...

-------------------------------------------------------------------------

Migrate replicas...

-------------------------------------------------------------------------

Migrate replication agreements...

-------------------------------------------------------------------------

Migrate key/cert databases...

-------------------------------------------------------------------------

Migrate Certmap.conf...

Where do you want to back up the file /export/home/jdoe/611-latest/shared/config/certmap.conf [/export/home/jdoe/611-latest/shared/config/certmap.conf_backup] ?

 

***** Close the LDAP connection to the new Directory Server instance *****
Shutting down server slapd-bart . . .

. . .

-------------------------------------------------------------------------

Data processing...

ldiffile: /export/home/jdoe/611-latest/slapd-bart/config//ldif/backend1.ldif
[12/Jun/2002:10:33:25 -0700] - export backend1: Processed 3 entries (100%).
[12/Jun/2002:10:33:25 -0700] - Waiting for 2 database threads to stop
[12/Jun/2002:10:33:26 -0700] - All database threads now stopped

ldiffile: /export/home/jdoe/611-latest/slapd-bart/config//ldif/backend2.ldif
[12/Jun/2002:10:33:29 -0700] - export backend2: Processed 3 entries (100%).
[12/Jun/2002:10:33:29 -0700] - Waiting for 1 database threads to stop
[12/Jun/2002:10:33:30 -0700] - All database threads now stopped

ldiffile: /export/home/jdoe/611-latest/slapd-bart/config//ldif/backend3.ldif
[12/Jun/2002:10:33:32 -0700] - export backend3: Processed 2 entries (100%)
[12/Jun/2002:10:33:32 -0700] - Waiting for 1 database threads to stop
[12/Jun/2002:10:33:33 -0700] - All database threads now stopped

Done.
[12/Jun/2002:10:33:37 -0700] - import backend1: Index buffering enabled with
bucket size 15
[12/Jun/2002:10:33:37 -0700] - import backend1: Beginning import job...
[12/Jun/2002:10:33:37 -0700] - import backend1: Processing file

"/export/home/jdoe/611-latest/slapd-bart/config//ldif/backend1.ldif"
[12/Jun/2002:10:33:37 -0700] - import backend1: Finished scanning file
"/export/home/jdoe/611-latest/slapd-bart/config//ldif/backend1.ldif" (3 entries)
[12/Jun/2002:10:33:40 -0700] - import backend1: Cleaning up producer thread...
[12/Jun/2002:10:33:40 -0700] - import backend1: Indexing complete.
Post-processing...
[12/Jun/2002:10:33:40 -0700] - import backend1: Flushing caches...
[12/Jun/2002:10:33:40 -0700] - import backend1: Closing files...
[12/Jun/2002:10:33:40 -0700] - import backend1: Import complete. Processed 3
entries in 3 seconds. (1.00 entries/sec)
[12/Jun/2002:10:33:44 -0700] - import backend2: Index buffering enabled with
bucket size 15
[12/Jun/2002:10:33:44 -0700] - import backend2: Beginning import job...
[12/Jun/2002:10:33:44 -0700] - import backend2: Processing file
"/export/home/jdoe/611-latest/slapd-bart/config//ldif/backend2.ldif"
[12/Jun/2002:10:33:44 -0700] - import backend2: Finished scanning file
"/export/home/jdoe/611-latest/slapd-bart/config//ldif/backend2.ldif" (3 entries)
[12/Jun/2002:10:33:44 -0700] - import backend2: Workers finished; cleaning up...
[12/Jun/2002:10:33:47 -0700] - import backend2: Workers cleaned up.
[12/Jun/2002:10:33:47 -0700] - import backend2: Cleaning up producer thread...
[12/Jun/2002:10:33:47 -0700] - import backend2: Indexing complete.
Post-processing...
[12/Jun/2002:10:33:47 -0700] - import backend2: Flushing caches...
[12/Jun/2002:10:33:47 -0700] - import backend2: Closing files...
[12/Jun/2002:10:33:47 -0700] - import backend2: Import complete. Processed 3
entries in 3 seconds. (1.00 entries/sec)
[12/Jun/2002:10:33:50 -0700] - import backend3: Index buffering enabled with
bucket size 15
[12/Jun/2002:10:33:50 -0700] - import backend3: Beginning import job...
[12/Jun/2002:10:33:51 -0700] - import backend3: Processing file
"/export/home/jdoe/611-latest/slapd-bart/config//ldif/backend3.ldif"
[12/Jun/2002:10:33:51 -0700] - import backend3: Finished scanning file
"/export/home/jdoe/611-latest/slapd-bart/config//ldif/backend3.ldif" (2 entries)
[12/Jun/2002:10:33:51 -0700] - import backend3: Workers finished; cleaning up...
[12/Jun/2002:10:33:54 -0700] - import backend3: Workers cleaned up.
[12/Jun/2002:10:33:54 -0700] - import backend3: Cleaning up producer thread...
[12/Jun/2002:10:33:54 -0700] - import backend3: Indexing complete.
Post-processing...
[12/Jun/2002:10:33:54 -0700] - import backend3: Flushing caches...
[12/Jun/2002:10:33:54 -0700] - import backend3: Closing files...
[12/Jun/2002:10:33:54 -0700] - import backend3: Import complete. Processed 2
entries in 4 seconds. (0.50 entries/sec)

-------------------------------------------------------------------------

Migrate Changelog...

-------------------------------------------------------------------------

***** Migrate ReplicaBindDN entries...

-------------------------------------------------------------------------

***** Migrate MultiplexorBindDN entries...

****** End of migration ******

1. Stop your Directory Server 6.x.
   
   
2. Install Directory Server 7.x.
   
   
3. Run the migration script as shown in section Migrating a Standalone Server.
   
   
4. Once your 6.x server is migrated, test replication to make sure it is working correctly.
   
   
5. After you finish this process for the supplier, repeat the steps for the consumers.

1. Stop directory writes on both suppliers.
   
   It is imperative that there are no entries being written or changed on the suppliers during the migration. After both the suppliers are migrated, writes can resume.
   
   
2. After stopping provisioning, make sure all changes have been replicated from the server to migrate to all of its consumers.
   
   Any changes left over in the changelog will be lost after migration, so make sure all changes in the changelog have been replicated to all consumers.
   
   
3. Migrate the first supplier; see section Supplier Migration.
   
   
4. Verify that writes and changes are being replicated through the servers.
   
   
5. Migrate the second supplier; see section Supplier Migration.
   
   
6. Verify that writes and changes are being replicated through the servers.
   
   
7. Migrate the hubs (if any); see section Hub Migration.
   
   
8. Verify that writes and changes are being replicated through the servers.
   
   
9. Migrate the consumers; see section Consumer Migration.
   
   
10. Verify that writes and changes are being replicated through the servers.

Supplier Migration

Follow these steps for the first supplier, and then repeat the steps for the second:

Hub Migration

To migrate a 6.x hub:

Consumer Migration

To migrate a 6.x consumer server:

1. Shut down the Administration Server and Directory Server.
   
   
2. Change these files to reflect server2's values:
   
   serverRoot/userdb/dbswitch.conf:directory default
   ldap://configHostname:configPort/o%3DNetscapeRoot
   
   serverRoot/admin-serv/config/adm.conf:ldapHost:configHostname
   serverRoot/admin-serv/config/adm.conf:ldapPort:configPort
   
   serverRoot/shared/config/dbswitch.conf:directory default
   ldap://configHostname:configPort/o%3DNetscapeRoot
   
   serverRoot/slapd-serverID/config/dse.ldif:nsslapd-pluginarg0:
   ldap://configHostname:configPort/o%3DNetscapeRoot
   
   
3. Turn off the Pass-through Authentication (PTA) Plug-in on server2 by editing its dse.ldif file.
   
   
   1. In a text editor, open this file:
      
      serverRoot/slapd-serverID/config/dse.ldif
      
      
   2. Locate the entry for the PTA plug-in:
      
      dn: cn=Pass Through Authentication,cn=plugins,cn=config
      
      
   3. Change nsslapd-pluginEnabled: on to nsslapd-pluginEnabled: off.
   
   
4. Restart the Directory Server and Administration Server.

Migrating Windows

The process of migrating Directory Server on Windows is slightly different than on UNIX platforms. The following sections describe how to migrate a standalone Windows Directory Server and Windows in a multi-master environment.


Migrating a Single Instance

1. Copy your Directory Server root over to a new directory. For example, copy the Netscape folder to a new folder named ds621.
   
   
2. Create a new folder to store the directory data, such as c:\data, and export all data to LDIF files in that directory by running the db2ldif.pl -r option:
   
   nsperl db2ldif.pl -D "cn=Directory Manager" -w secret -p 389 -n userroot -r -a c:\data\userroot.ldif -s "dc=example,dc=com"
   
   Do this separately for each instance of the old Directory Server. The data directory should contain one LDIF file for each backend; for example, userRoot.ldif, exampleRoot.ldif, and so on.
   
   
3. Uninstall the old Directory Server.
   
   
4. If necessary, upgrade the operating system of the machine. For example, upgrade to Windows 2000, Service Pack 4, from Windows NT.
   
   
5. Install Directory Server 7.0.
   
   
6. Run the migration script, specifying the migration data directory (-d). The command syntax for running the script is shown below:
   
   nsperl migrateInstance7 -D rootDN -w password -p port -o oldInstancePath -n newInstancePath -d "oldDataDirectoryPath"
   
   You must quote the data directory for the import to work properly. An example command is shown below:
   
   nsperl migrateInstance7 -D "cn=Directory Manager" -w secret -p 389 -o c:/ds621/servers/slapd-phonebook -n c:/netscape/servers/slapd-phonebook -d "c:/data"
   

Migrating a Multi-Master Scenario

If you are migrating a Directory Server 6.x multi-master replication environment to Directory Server 7.0, note the following:

• During the migration of the replication agreements, the migration script will output a non-fatal error that states The filename, directory name, or volume label syntax is incorrect. Because of this error, all the replication agreements will have an invalid password configured in them after migration. To fix the problem, in the Directory Server Console, select the replication agreement and use the Connection tab to change the password. After you change the password, replication will automatically resume with no need for a reinitialization. The password does not need to be reconfigured in the Replication Manager entry in dse.ldif.
  

Note	You must import your database LDIF files at the time of migration using the -d option. If you do not, your creation times for the entries will hang, and replication will not resume.

To migrate a Windows supplier:

1. Copy your Directory Server root over to a new directory. For example, copy the Netscape folder to a new folder named ds621.
   
   
2. Create a new folder to store the directory data, such as c:\data, and export all data to LDIF files in that directory by running the db2ldif -r option.
   
   Do this separately for each instance of the old Directory Server. The data directory should contain one LDIF file for each backend; for example, userRoot.ldif, exampleRoot.ldif, and so on.
   
   
3. Uninstall the old Directory Server.
   
   
4. If necessary, upgrade the operating system of the machine. For example, upgrade to Windows 2000, Service Pack 4, from Windows NT.
   
   
5. Install Directory Server 7.0.
   
   Make this your configuration instance since it is not replicated. For the other suppliers, register against the first supplier’s configuration instance.
   
   
6. Log into the Console, and create a new instance to which you are going to migrate.
   
   This instance will need to be created to listen on the port to which your standard access will be (usually 389).
   
   
7. Run the migration script, following the instructions in Migrating a Single Instance.
   
   
8. Once your supplier is migrated, test replication to make sure that it is working correctly.
   
   
9. After you finish this process for the first supplier, repeat the steps for the other suppliers.
   
   You may wish to set up multi-master replication for o=NetscapeRoot between the high port instances on the suppliers.
   

To migrate a Windows hub:

1. Copy your Directory Server root over to a new directory. For example, copy the Netscape folder to a new folder named ds621.
   
   
2. Create a new folder to store the directory data, such as c:\data, and export all data to LDIF files in that directory by running the db2ldif -r option.
   
   Do this separately for each instance of the old Directory Server. The data directory should contain one LDIF file for each backend; for example, userRoot.ldif, exampleRoot.ldif, and so on.
   
   
3. Uninstall the old Directory Server.
   
   
4. Install Directory Server 7.x to a high port, registering against the first supplier’s configuration instance.
   
   
5. Run the migration script, following the instructions in Migrating a Single Instance.
   
   
6. Once your hub is migrated, test replication to make sure that it is working correctly.
   
   
7. After you finish this process for the first hub, repeat the steps for any additional hubs.
   

To migrate a Windows consumer server:

1. Copy your Directory Server root over to a new directory. For example, copy the Netscape folder to a new folder named ds621.
   
   
2. Create a new folder to store the directory data, such as c:\data, and export all data to LDIF files in that directory by running the db2ldif -r option.
   
   Do this separately for each instance of the old Directory Server. The data directory should contain one LDIF file for each backend; for example, userRoot.ldif, exampleRoot.ldif, and so on.
   
   
3. Uninstall the old Directory Server.
   
   
4. Install Directory Server 7.x to a high port, registering against the first supplier’s configuration instance.
   
   
5. Run the migration script; see Migrating a Single Instance.
   
   
6. Once your consumer is migrated, test replication to make sure that it is working correctly.
   
   
7. After you finish this process for the first consumer, repeat the steps for any additional consumers.