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.
Before continuing, back up all volumes that you are not planning to migrate, ensure the following, and then click:
All volume data migrated successfully
All critical errors from the file copy are resolved
The servers in your source tree are in time synchronization and eDirectory is synchronized
Verify that you have run the DSRepair procedures in Section 10.2, Preparing the Source Server for Migration to ensure that the eDirectory tree containing the source server is functioning correctly.
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, indicate whether you want the Migration Wizard to update the source server's schema and then click.
is the default selection. This causes the Migration Wizard to compare the source and destination schemas and update the source server's schema to include the eDirectory classes of the default applications that are installed on the destination server. You must be logged in as a user with all rights to the [Root] of the tree to make these changes.
If you do not have the necessary rights to extend the schema, select. The migration continues, but you might experience some problems with your eDirectory tree if you skip this procedure.
In the Verify Novell Directory Services Tree dialog box, select Step 2).to acknowledge that the source eDirectory tree is healthy (you should have run the DSRepair procedures in
If you select, 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.
To ensure the security certificate works properly on the destination server, indicate how you want to copy the source server’s NICI configuration files to the destination server and then click.
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.
To copy the nuwnici.nlm file to the source and destination servers, click and then click .
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.
HINT:If you get NICI errors when eDirectory tries to load or when you copy the NICI files, check to see if pki.nlm will load on the destination server. If it won’t load, see Section 12.9, NICI Errors.
Delete all user connections (except your own) to the source and destination servers, then click.
If you want to first broadcast a logout message to any users logged in to the server, select, type the message in the field, and then click .
Type the passwords for the source and destination trees, then click.
Resolve any critical errors or warnings on the Migrate NDS/eDir Verification Results screen, then click.
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 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 Section 12.11, NDS/eDirectory Migration Failures.
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:
The file server name is changed to the name of the source server.
The time zone is changed to the one stored in the source server’s autoexec.ncf file.
The server ID is changed to the IPX™ internal net value or server ID stored 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
IMPORTANT:During the migration, the source server’s Timesync information is not automatically migrated.
This step backs up eDirectory and copies the eDirectory backup files to the destination server and to sys:system\nuw30\ndsbu on the source server.
Down the source server by clicking.
The Source Server Status dialog box displays.
Verify that the source server is down by selecting.
This step removes eDirectory from the destination server and deletes the client connection.
This step upgrades eDirectory on the destination server if necessary, restores eDirectory on the destination server, and prepares to reboot the destination server.
Reboot the destination server by clicking.
When you are ready to proceed, select> .
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 Section 12.2, Workstation-to-Server Connection Problems.
Restart the Migration Wizard utility.
Read the About screen, then click.
The utility verifies that the first three steps of the project file are complete.
Selectwhen prompted if you are ready to proceed to the fourth step.