Supplier Migration - Netscape DIRECTORY SERVER 7.0 Installation Manual

The migration process can be summarized into these steps:
Stop directory writes on both suppliers.
1.
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.
After stopping provisioning, make sure all changes have been replicated from
2.
the server to migrate to all of its consumers.
Any changes left over in the
sure all changes in the
Migrate the first supplier; see section "Supplier Migration‚" on page 85.
3.
Verify that writes and changes are being replicated through the servers.
4.
Migrate the second supplier; see section "Supplier Migration‚" on page 85.
5.
Verify that writes and changes are being replicated through the servers.
6.
Migrate the hubs (if any); see section "Hub Migration‚" on page 86.
7.
Verify that writes and changes are being replicated through the servers.
8.
Migrate the consumers; see section "Consumer Migration‚" on page 86.
9.
Verify that writes and changes are being replicated through the servers.
10.

Supplier Migration

Follow these steps for the first supplier, and then repeat the steps for the others:
Stop the 6.x Directory Server.
1.
Install Directory Server 7.x.
2.
Make this your configuration instance since it is not replicated. For the other
suppliers, register against the first supplier's configuration instance.
Log into the Console, and create a new instance to which you are going to
3.
migrate.
This instance will need to be created to listen on the port to which your
standard access will be (usually
Run the migration script following the instructions in "Migrating a Standalone
4.
Server‚" on page 76.
will be lost after migration, so make
changelog
have been replicated to all consumers.
changelog
).
389
Chapter 6
Migration Procedure
Migrating from Previous Versions 85