9.3 Migration Procedure

  1. Run the migedir utility by entering the following command on the target server:

    migedir -s <IP address> [-A <log directory name>] [-t] [-v] [-h]

    The utility takes the following command line options:



    -s IP address

    Specifies the IP address of the source server containing the eDirectory instance to be migrated.

    IMPORTANT:-s is a mandatory parameter.

    -A directory name

    Enables auditing. directory name specifies the directory in which log files should be created.


    Tests the validity of the input parameters.

    NOTE:This option verifies the IP address. However, it does not perform the actual migration.


    Enables the verbose mode.


    Prints help about using this utility.

  2. Follow the on-screen instructions as the utility performs the migration.

    The migration utility does some pre-migration checks, performs the migration, then does some post-migration tasks.


The utility performs the following checks:

  • The health and state of the replicas in the ring are verified.

  • Configuration information for the server being migrated is collected and written to a configuration file to be used by other operations during the migration.

  • Time synchronization is verified between the source and target servers.

  • The target server is checked for any existing eDirectory instances.

    • If the instance exists, the user is prompted and the existing instance is removed before proceeding with the migration.

    • If the instance does not exist, a new instance is configured and used.


The utility performs the migration of the eDirectory instance from the collected configuration information. This involves backing up the source server data, locking the eDirectory instance in the source server, migrating data to the target server, and restoring the eDirectory instance on the target server. The dependent NICI files are also migrated.

The utility also configures the local instance in the target server with the source server details obtained during the previous checks.


After migration, the following tasks are performed by the utility:

  • The nds.conf configuration file is modified with the source server eDirectory instance information, such as tree name and server name.

  • The eDirectory instance in the target server is restarted so it can use the new data.

  • Network address repair is performed to start the synchronization of the new IP address in the replica ring.

Handling Failures

During migration, the database in the source server is locked to avoid multiple copies of the instance running on the source and target servers. Multiple copies of the same instance can lead to data inconsistency. If the process fails and if you intend to bring up the source server again, you need to perform the following tasks:

  1. Remove the partially migrated eDirectory instance on the target server.

    For more information on how to remove the eDirectory instance from a server, see Using the ndsconfig Utility to Add or Remove the eDirectory Replica Server.

  2. Restore and unlock the database in the source server.

    For more information on how to unlock and restore the database, see Using the eMBox Client for Backup and Restore in the NetIQ eDirectory 8.8 SP8 Administration Guide.

    The database backup is saved in the sys:ni/data folder.