Installation guide

Migration Procedure
Chapter 6 Migrating From Previous Versions 63
Migration Procedure
The migration script will automatically back up your Directory Server
configuration.
• If you are migrating from Directory Server 4.x, all of the files with a
.conf
extensioninthe/usr/netscape/server4/slapd-serverID directoryarebacked
up.
• If you are upgrading from Directory Server 5.0, all of the configuration fil es in
/usr/netscape/servers/slapd-serverID/config will be backed up to a
directory named
/usr/netscape/servers/slapd-serverID/config_backup.
• If your configuration files are stored in non-default locations, before you
migrate y our server, copy them t o a safe place.
Once you have backed up your critical configuration information, do the following
to migrate a server:
1. Stop your legacy Directory Server.
If you do not s top 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
Directory Server.
The installation process is described in Chapter 3, “Using Express and Typical
Installation,” or Chapter 4, “Silent Installation.”
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 di rectory server port numbers) will continue to work.
3. Run the migration script. As root user (on UNIX), change directory to
/usr/netscape/servers/bin/slapd/admin/bin. Then enter the following
command:
On UNIX:
migrateInstance6 -D rootDN -w passwd -p port -o oldServerPath -n
newServerPath
where:
❍ rootDN is the DN for Directory Manager in Directory Server 6.02
❍ passwd is the password for Directory Manager in Directory Server 6.02
❍ port is the LDAP port number in Directory Server 6.02