Installation guide

9
Migrating eDirectory from NetWare to OES 2 Linux 95
9
Migrating eDirectory from NetWare to
OES 2 Linux
eDirectory migration from NetWare requires the migration of eDirectory data and server identity to
provide seamless accessibility after migration.The eDirectory migration utility performs all of the
pre-migration tasks, health validations and server backups, server migration tasks, and post-
migration tasks for you.
The following sections give you more details on the migration procedure for eDirectory. For more
information, see the Novell Open Enterprise Server Migration Web site (http://www.novell.com/
products/openenterpriseserver/migrate.html) and the OES 2 SP3: Upgrading to OES - Best Practices
Guide (http://www.novell.com/documentation/oes2/upgrade_to_oes_lx/data/front.html).
 Section 9.1, “Planning Your Migration,” on page 95
 Section 9.2, “Migration Tools,” on page 96
 Section 9.3, “Migration Procedure,” on page 96
 Section 9.4, “After the Migration,” on page 98
9.1 Planning Your Migration
This section lists the important requirements that must be verified before attempting eDirectory
migration.
 Section 9.1.1, “System Requirements,” on page 95
 Section 9.1.2, “Prerequisites,” on page 95
 Section 9.1.3, “Supported Platforms,” on page 96
9.1.1 System Requirements
 The target server must run OES 2 and should have the eDirectory 8.8 SP8 RPMs already
installed.
 If the target OES 2 server has a default eDirectory 8.8 SP8 instance already configured, this
instance should be active. This instance will be overwritten after the migration.
 OES 2 does not support multiple instances of eDirectory on the same server, so any non-default
instances should not be running during migration.
 The source NetWare server should be running and should not be part of any partition operation.
9.1.2 Prerequisites
 The eDirectory migration utility will run only on the target server and must be able to access the
NetWare server remotely.