The Begin NDS/eDirectory Migration step migrates the eDirectory files from the source server to the destination server. The source server is brought down and the destination server is restarted during this step.
In the Project View dialog box, click Begin NDS/eDir Migration.
Before continuing, back up all volumes that you are not planning to migrate and ensure the following:
Verify that you have run the DSRepair procedures in Preparing the Source Server for Migration to ensure that the eDirectory tree containing the source server is functioning correctly. Then click Next.
HINT: If you are required to fix any eDirectory errors, wait approximately 30 minutes for the eDirectory tree to synchronize before continuing.
In the Update Schema dialog box, select whether you want the Migration Wizard to update the source server's schema, then click Next.
In the Verify Novell Directory Services Tree dialog box, click Yes to acknowledge that the source eDirectory tree is healthy (you should have run the DSRepair procedures in Step 2).
If you click No, the Migration Wizard does not prevent you from continuing. However, if your tree is unhealthy before you begin the migration, the migration might not complete successfully.
You are now prompted to copy and transfer the NICI configuration files from the source server to the destination server.
To ensure the security certificate works properly on the destination server, you must copy the source server's NICI configuration files to the destination server. To facilitate the NICI file copy, nuwnici.nlm is first copied to both the source and destination servers.
You can choose to copy the NICI files Automatically (Over the network) or using a diskette swap. Select the radio button next to the method you want, then click Next.
(Conditional) If you selected the diskette swap, continue with Step 6.a. If you selected the automatic copy over the network, proceed to Step 7.
To copy the nuwnici.nlm to the source and destination servers, click Copy NLM.
Click Next.
Insert a blank formatted diskette into the floppy drive on the destination server.
At the destination server console, enter load nuwnici -1.
Remove the diskette from the destination server and insert it into the source server's floppy drive.
At the source server console, enter load nuwnici -2.
This copies the NICI files to the diskette.
Remove the diskette from the source server and insert it into the destination server's floppy drive.
At the destination server console, enter load nuwnici -3.
This copies the NICI files to the destination server.
Click Next.
HINT: If you get NICI errors when eDirectory tries to load or when you copy the NICI files, check and see if pki.nlm will load on the destination server. If it won't load, see NICI Errors.
Delete all user connections (except your own) to the source and destination servers, then click Next.
If you want to first broadcast a logout message to any users logged in to the server, click Broadcast Logout Message, type the message in the field, and then click OK.
Type the passwords for the source and destination trees, then click Next.
Resolve any critical errors or warnings on the Migrate NDS/eDir Verification Results screen, then click Next.
Perform the eDirectory step-by-step migration.
The eDirectory migration is divided into several steps. This is for diagnostic purposes. If the eDirectory migration fails for any reason, you will know exactly what step it failed on and can take the appropriate measures to fix the problem.
For more information on the NDS/eDirectory migration process, including steps to restore the source and destination servers, see NDS/eDirectory Migration Failures.
Click Next.
The first step changes autoexec.ncf and timesync.cfg; modifies the server name in hosts, hostname, and snmp.cfg; and renames smdr.cfg to smdr.mig. The first step also renames rootcert.der in both the sys:system and sys:public directories to rootcert.der.bak.
At the end of the migration process, the source server is brought down and the destination server reboots and takes over the name and identity of the source server.
Migration Wizard automatically modifies the following items in the destination server's autoexec.ncf file:
IMPORTANT: During the migration, the source server's Timesync information is not automatically migrated.
To begin the next step (backing up eDirectory, copying the eDirectory backup files to the destination server, and copying the eDirectory backup files to sys:system\nuw30\ndsbu on the source server), click Next.
Down the source server by clicking Next.
The Source Server Status dialog box displays.
Verify that the source server is down by clicking Yes.
To begin the next step (removing eDirectory from the destination server and deleting the client connection), click Next.
To begin the next step (upgrading eDirectory on the destination server if necessary, restoring eDirectory on the destination server, and preparing to reboot the destination server), click Next.
Reboot the destination server by clicking Next.
If you are ready to proceed, click Yes > Finish.
Check the former destination server and verify that it has restarted and taken on the name of the source server. The server console prompt should display the source server's name.
Exit the Migration Wizard. (The project file is automatically saved.)
Reboot your workstation and log in to the former destination server.
This clears old connections from the workstation and establishes a clean connection to the former destination server.
If you can't log in, refer to Workstation-to-Server Connection Problems.
Restart the Migration Wizard utility.
Read the About screen, then click OK.
Click Open Last Project > OK.
The utility verifies that the first three steps of the project file are complete.
When prompted if you are ready to proceed to the fourth step, click Yes.