Step 4: eDirectory Migration

After you have finished migrating the data volumes and configuration files, it's time to tackle eDirectory. During this step, the source server is brought down and the destination server is restarted. Furthermore, the destination server takes on the source server's name and place in your network. Pretty cool, huh? Following is a preview of the changes that Migration Wizard makes to the destination server's AUTOEXEC.NCF file:

• The server name changes to the name of the source server.

• The time zone is changed to the time zone in the source server's AUTOEXEC.NCF file.

• The server ID changes to the IPX internal network number or server ID in the source server's AUTOEXEC.NCF file.

• The default time server type is changed to the value stored in the source server's AUTOEXEC.NCF file.

• The bindery context is changed to the bindery context stored in source server's AUTOEXEC.NCF file.

Let's continue on the Project Migration journey.

Beginning NDS Migration

Your third task using the Migration Project Window is to click the Begin NDS Migration button. When you do, the Migration Wizard requests licensing information and then updates the source server's Schema to include the eDirectory classes of the default applications that are installed on the destination server. If you select No to update the Schema, Migration Wizard will compare the source and destination Schemas instead. This comparison helps you to determine how to extend your Schema manually. Click Yes to continue.

Next, the Wizard will ask you if your eDirectory tree is healthy. This screen is a simple reminder to run DSREPAIR prior to migration. The Migration Wizard does not prevent you from continuing if you have not run DSREPAIR; however, the migration might not complete successfully if your eDirectory tree is unhealthy. Click Yes to continue.

If you are migrating from NetWare 4 running Border Manager, or NetWare 5, or NetWare 6, you will be prompted to copy and transfer the NICI configuration files from the source server to the destination server. Begin this process by selecting Copy NLM. When you see the confirmation message, click OK to continue. Then, NICI will be automatically configured.

Now it's time for action. Next, the Migration Wizard will delete all user connections (except yours) to the source and destination servers. Click Next to continue. Finally, the Wizard will prompt you to authenticate with your source and destination username and password and resolve any critical (denoted by a red circle with a white "X") and noncritical (denoted by a yellow triangle) errors. When you have performed all of the eDirectory migration tasks, you can actually perform the migration by clicking the Migrate button.

REAL WORLD

During the NetWare 6 migration, your trustee assignments might not be fully restored to User and Group objects the first time you run Finish NDS Migration. This is because NSS volumes depend on the NDS backlink process to create ID information on objects before trustees can be associated with those objects. Therefore, you must verify that the backlink process is complete before running Finish NDS Migration.

If you have run Finish NDS Migration and are missing trustees, you can manually complete the backlink process and rerun Finish NDS Migration. Reboot the server after this step completes. To manually run the backlink process, enter the following commands at the server console:

 SET DSTRACE=ON SET DSTRACE=+BLINK SET DSTRACE=*B 

Finishing NDS Migration

Next, you will click the Finish NDS Migration button in the Migration Project Window. When you do, the Migration Wizard displays the Continue NDS Migration window. Make sure to validate that the former destination server has restarted, that it has the identity of the source server, and that licensing is installed before you continue.

Next, you must ensure that eDirectory is synchronized on all servers in the tree. To check eDirectory synchronization status, enter DSREPAIR at the server console and run the Report Synchronization Status and Time Synchronization options. If the destination server does not contain a Read/Write or Master replica, you must check eDirectory synchronization by running DSREPAIR on another server in the eDirectory tree that has one of these replicas.

Then, at the end of the NetWare 6 Migration, verify that you have completed these tasks by selecting Yes. Finally, authenticate to the source tree, resolve any critical and/or noncritical errors, and, complete the migration by clicking Continue.

At this point, the Migration Complete dialog box appears. Click View Success Log and review the information listed. Click the close button (X) to close the window. Again, the Migration Complete dialog box reappears. Click Done.

That's all there is to it!