17.3 Migration Procedure

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

    migedir [-A <log directory name>] [-s <IP address>] [-t] [-h] [-i] [-u] [-a] [-w] [-B] [-R]

    The utility takes the following command line options:



    -A directory name

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

    -s IP address

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

    IMPORTANT:-s is a mandatory parameter.


    Tests the validity of the input parameters.

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


    Prints help about using this utility.


    Enables the verbose mode.


    Enables the unattended mode.


    Specifies the tree adminDN.


    Specifies the admin password.


    Enables the Backup Only mode.


    Enables the Restore Only mode.

  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.

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


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.


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 removing the eDirectory instance from a server, see Removing a Server Object And Directory Services From a Tree in the NetIQ eDirectory Installation Guide.

  2. Bring up the source server by reloading the directory services. Make sure that the source server is brought up on the network only when the migration fails. The database backup and log files are saved in the SYS:\ folder.