Migrate NetWare 4 and NetWare 5 Servers to NetWare 6: Part 2

Articles and Tips: article

01 Feb 2003

From Course 3005: Advanced Novell

Network Management: NetWare 6

Last month, we started covering how to use the NetWare migration wizard utility and discussed preparing for and running the Migration Wizard. This month, we'll finish up by showing you how to edit the configuration files, perform the eDirectory migration, perform post-migration tasks. And if there's room, this installment will show how to troubleshoot post-installation issues.

Edit Configuration Files

Next, you compare the source server and destination server configuration files. You also edit the configuration files on the destination server. To edit the configuration files, do the following:

In the Project Window, select Edit Configuration Files. The migration wizard lets you modify any NCF or CFG files on the destination server. These files contain default LOAD statements and parameters.

If you are editing the AUTOEXEC.NCF file, make sure the file is closed before you migrate your eDirectory database.
Select the configuration file you want to edit; then select Edit File (see Figure 1).

Comparing the lines in the AUTOEXEC.NCF file
Copy and paste the commands from the configuration file on the source server to the corresponding configuration file on the destination server.

If you intend to change the IP address on your destination server to be the same as the IP address of your source server, edit your configuration files and change the IP address in 3 places:

AUTOEXEC.NCF SYS:\ETC\HOSTNAME SYS:\ETC\HOSTS:

Copy the source server's IP address and paste it into the destination server's AUTOEXEC.NCF file.

Note: This works only if your IP LOAD and BIND statements are in AUTOEXEC.NCF. If you use INETCFG to assign IP addresses, change the IP addresses after the migration is complete.

Using EDIT.NLM at the server console of the destination server, change the IP address in the SYS:\ETC\HOSTS and SYS:\ETC\HOSTNAME files.

When you finish modifying your configuration file, select Save & Close.
Close the Compare Configurations dialog.

Begin the eDirectory Migration

After you complete the volume copy and edit the configuration files, you can migrate eDirectory from the source to the destination server. During this phase, the source server is brought down and the destination server is restarted. The destination server takes the source server's name and place in your network.

To begin the eDirectory migration, do the following:

In the Project Window, select Begin NDS Migration (see Figure 2)

Steps to perform as you begin NDS migration
.Back up all volumes that you are not planning to migrate and complete the following tasks before continuing; then select Next:
- Make sure all volume data migrated successfully
- Make sure all critical errors from the file copy are resolved
- Make sure that the time is synchronized on the servers in your source tree and that eDirectory is synchronized
For more information, see step 2 in "Finish eDirectory Migration."
When the Install License window appears, insert the license disk and browse to or enter the path to the license file; then select Next. If you have an MLA, you can select the MLA instead of inserting the license disk.
Update the source server's schema by selecting Yes; then select Next. The migration wizard updates the source server's schema to include the eDirectory classes of the default applications that are installed on the destination server. (See Figure 3)

Comparing and updating schema.
Note: If you select No to update the schema, by default the second Yes option is enabled, which causes the migration wizard to compare the source and destination schemas.

Note: This comparison helps you determine how to extend your schema in preparation for the migration.
In the Verify Novell Directory Services Tree window, verify that you have run DSREPAIR to verify that the eDirectory tree containing the source server is functioning correctly; then select Yes or No to acknowledge that your tree is healthy; then select Next.

Note: The migration wizard does not check the health of the tree and will not prevent you from continuing if your tree is unhealthy. If your tree is unhealthy the migration might not complete successfully.
In the Copy NICI Configuration Files window, select Copy NLM to begin the process of copying your NICI files.
When you see the message that NUWNICI.NLM was copied to the destination server from the source server, select OK.
Copy the NICI files from the source server to the destination server by following the on-screen instructions. When the NICI configuration is complete, the screen in Figure 4.

Steps to complete the copying of the NICI files
Delete all user connections (except your own) to the source and destination servers; then select Next.
In the Password Verification window, enter the passwords for the source and destination trees; then select Next.
Resolve any critical errors or warnings shown in the Migrate NDS Verification Results screen; then select Next.
In the Ready to Migrate NDS window, select Migrate to begin the migration. At the end of the migration, the source server is brought down and the destination server reboots and takes over the name and identity of the source server. The migration wizard modifies the following items in 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 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.
When the migration is complete, view the Error and Success logs; then select Done. Use the Error log to see errors that occurred during migration. If there were errors, use the Success log to determine how far the migration progressed.

If migration failed, restore your servers to their original configuration.
Check the destination server and verify that it has restarted and taken on the name of the source server.
Reboot your workstation and log in to the former destination server.

Finish the eDirectory Migration

In this phase you upgrade the schema, fix volume objects, and restore trustees to the destination server after the server is restarted. To finish the migration, do the following:

In the Project Window, select Finish NDS Migration.

In the Project Window at the Finish NDS Migration phase, notice that all buttons but the Finish NDS Migration button are gray. These options are gray because the source server has been migrated to the destination server. You cannot go back and redo the steps described in these options.
Read the Continue NDS Migration window and make sure the following has happened; then select Next:
- The former destination server has restarted and has the name and identity of the source server.
- Licensing is installed.
- 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, check eDirectory synchronization by running DSREPAIR on another server in the eDirectory tree that has one of these replicas.
Verify that you have completed the tasks by selecting Yes or No; then select Next (see Figure 5).

Continuing NDS migration
In the Password Verification window, enter the password for the source tree; then select Next.
Resolve any warnings or errors; then select Next.
Finish the eDirectory migration by selecting Continue. During this stage, the migration wizard restores the file trustees and updates the volume objects in the tree.
View the error and success logs; then select Done to close the current project.

Perform Post-Migration Tasks

After the migration is complete, you need to perform the following to ensure that your new NetWare 6 network is running properly:

Run the External Reference Check Process
Upgrade Existing NSS Volumes
Perform Other Post-Installation Tasks

Run the External Reference Check Process.

An external reference is a pointer to an eDirectory object on another server. An external reference indicates that an object in a replica has an ID on a server where the replica doesn't exist. The external reference check process is an eDirectory process that verifies external references.

When migrating, trustee assignments might not be fully restored to user and group objects. NSS volumes depend on the eDirectory external reference check process to create ID information on objects before trustees can be associated with those objects.

To manually run the external reference check process, enter the following at the server console:


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

If you switch to the Directory Services screen on the server, you can watch the objects as they are processed.

Note: You can also run the external reference check process using iMonitor.

These commands must be repeated until no more user or group objects appear in the external reference list on the Directory Services screen. When complete, reboot the server.

Upgrade Existing NSS Volumes.

If the original server had NSS volumes, you need to upgrade them to be compatible with the version of NSS shipped with NetWare 6.

Note: If you migrate volume SYS, volume SYS remains a traditional volume until you upgrade it to NSS.

To upgrade existing NSS volumes, do the following for each NSS volume:

(For an in-place upgrade only) At the command prompt enter:
```
			NSS /ZLSSVOLUMEUPGRADE=All
```
At the server console, enter:
```
			SET NLS SEARCH TYPE
```
Make sure the value for NLS SEARCH TYPE is set to 0; if not, at the console prompt enter
```
			SET NLS SEARCH TYPE = 0
```

At the server console, enter:


			SET STORE NETWARE 5 CONN SCL MLA
			USAGE IN NDS

Make sure the value is set to OFF; if not, enter:


			SET STORE NETWARE 5 CONN SCL MLA
			USAGE IN NDS = OFF

At the server console prompt, enter:


			FLUSH CDBE

CDBE stands for CDBE.NLM or NetWare Configuration DataBase Engine.

Perform Other Post-Installation Tasks.

After a NetWare 6 migration or upgrade, you also need to perform the following tasks:

Run DSREPAIR on the destination server and select Unattended Full Repair.
Make sure user information was migrated or upgraded successfully.
Reinstall applications that have files or NLMs associated with the following SYS directories: SYSTEM, PUBLIC, MAIL, ETC, and NETBASIC.

Because the source server's identity replaces the destination server during a migration, eDirectory objects on the destination server, including those representing applications, are removed and replaced by objects that exist on the source server.

However, the NLMs associated with the destination server's applications still exist. Because you can't manage applications without their eDirectory objects, you must reinstall the applications to restore their objects to the tree.

Troubleshoot Post-Installation Issues

This part provides information regarding the following known issues:

Issues	Solutions
Missing device drivers	The server installation program copies to a startup directory (C:\NWSERVER) only drivers (such as HAMs, CDMs, and PSMs) for devices that were auto-detected during the installation process. If you attempt to load a HAM, CDM, or PSM that was not auto-detected during installation and it fails to load, copy the appropriate driver from the C:\NWSERVER\DRIVERS directory to the C:\NWSERVER directory and then load the driver again.
Status of old LAN and WAN files	After an upgrade to NetWare 6, old LAN and WAN files will not be deleted. These old files might not be supported in a NetWare 6 environment.
Speeding up the post-installation utility	If performance of the post-installation utility and other Java applications is slow, change the VM Cache Pool Percentage SET parameter by entering the following at the server console: SET VM CACHE POOL PERCENTAGE = 30 The performance of the post-installation program and some Java applications improves significantly with this change.The changes are saved by the operating system and remain even if the server is rebooted.
Update SMS components	A new release of Storage Management Services (SMS) is available on the Novell Support web site. This release contains important fixes to the SMS components delivered with NetWare 6. The fixes ensure compatibility between earlier versions of NetWare and the NetWare 6 SMS modules. In addition, the patch includes updates to SMS components (including SMDR and TSA), which have made the product more stable and robust. To maintain backup and restore services on NetWare 6 and your network, you must install the patch. The patch will supersede the SMS modules installed by default during the NetWare 6 installation. For more information, see the Readme included with the patch.
Agent Installation for GroupWise 6 replaces LDAP files needed by iFolder	The Agent Installation program for GroupWise 6 lets you overwrite LDAP modules that disable iFolder running on NetWare 6. To avoid this problem, select No when prompted to overwrite the LDAP modules during GroupWise agent installation. The LDAP module includes: LDAPSDK.NLM LDAPSSL.NLM LDAPX.NLM If these files are overwritten (by selecting Yes), you must manually copy the files from the NetWare 6 Operating System CD before iFolder will run on NetWare 6.
Missing user licenses	NetWare 6 requires you to install user licenses separately from the server license. After migrating to NetWare 6, use iManager to install license certificates when you add NetWare servers and users to the eDirectory tree.

For issues that can happen before and during installation and migration, see Known Issues at the NetWare 6 documentation web site athttp://www.novell.com/documentation/lg/nw6p/index.html .

* Originally published in Novell AppNotes

Disclaimer

The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.