This section lists the important requirements that must be verified before attempting eDirectory migration.
The target server must run OES 23.4 with the migration pattern selected.
OES 2015 or later does not support multiple instances of eDirectory on the same server, so any non-default instances should not be running during migration
The source server should be running and should not be part of any partition operation. For more information on supported source server versions, refer to the eDirectory Coexistence and Migration
in the OES 23.4: Planning and Implementation Guide.
The eDirectory migration utility can run only on the target server and must be able to access the source server remotely.
All servers that share a replica with the server to be restored are up and communicating. This allows the restore verification process to check with servers that participate in the same replica ring.
For more information, see Preparing for a Restore
in the NetIQ eDirectory Administration Guide.
The eDirectory migration utility is designed to run on OES 2015 or later, which is the target platform for migration. For more information on the compatible eDirectory versions at the source and the corresponding target servers, refer to the Prerequisites and Support Matrix for NetWare and OES Services.
IP address and DNS migrations are not performed by this migration utility.
Only the eDirectory instance is migrated. Applications depending on eDirectory are not migrated by this utility.
You should not use this migration methodology if you want both the servers to be available during the migration operation.
NOTE:Only the target server is available after the Transfer ID migration. The eDirectory DIB on the source server is locked. Other service migrations cannot be performed after completing Transfer ID migration for eDirectory. The source server can be brought back by restarting the eDirectory server, but you should do this only if the Transfer ID migration is unsuccessful.