Migrating A Replicated Site - Netscape DIRECTORY SERVER 6.02 Installation Manual

Migrating a Replicated Site

The following is an example of a command you would use on a UNIX machine
to migrate a 4.11 Directory Server to Directory Server 6.02:
migrateInstance6 -D "cn=Directory Manager" -w secret -p 1389
-o /usr/netscape/server4/slapd-coolwave
-n /usr/netscape/servers/slapd-coolwave
Provide a path and filename for your backup directory, or accept the default.
4.
The following is an extract of the script's output:
Parse the configuration file:
/space/netscape/server4_11/slapd-coolwave/config/slapd.conf...
Suffix o=example.com doesn't exist
Backend: MigratedDB_0 has been created !!!
Suffix dc=example,dc=com doesn't exist
Backend: MigratedDB_1 has been created !!!
For the suffix o=NetscapeRoot, we do nothing
Update general server parameters...
Update successfully passwordHistory
Update global LDBM parameters...
Update successfully nsslapd-mode
Update specific backend parameters...
Migrate DSE entries...
Migrate attributes...
Migrate objectclasses...
Migrate indexes...
Migrate plugin's...
Your legacy Directory Server is then migrated. As a result of this migration, a new
Directory Server 6.x instance is installed using the configuration information
obtained from your legacy Directory Server. In addition, the data from your old
server is migrated to the new server and the new server is started.
Migrating a Replicated Site
If you are upgrading from Directory Server 5.0 to Directory Server 6.x, your
replication configuration is automatically migrated when you run the
migrateInstance6
64 Netscape Directory Server Installation Guide • May 2002
oldServerPath is the path to the legacy Directory Server directory (for
example,
/usr/netscape/server4/slapd-serverID
newServerPath is the path to the Directory Server 6.02 directory (for
example,
/usr/netscape/servers/slapd-serverID
script.
)
)