| NetWare 6 migration is serious business. As such, it requires some careful preparation and you'll need to accomplish some important premigration preparation tasks before you can get started (floppy diskette required). Here's a quick preview: Source Server Preparation The NetWare 6 Migration process requires that you prepare both the source and destination servers in unique ways. In this first step, we will learn how to prepare the source server with ConsoleOne, name space, and DSREPAIR. Destination Server Preparation Then, we will shift our focus to the destination server. This server must be installed into a temporary eDirectory tree and prepared for all the exciting new information it is about to receive. Verify the Migration Client Finally, you'll need to verify the Novell Client version running on your migration client. This can be accomplished in a number of ways.
Let's explore step 1 in more detail. Ready, set, prepare! Source Server Preparation NetWare 6 Migration requires two types of preparation: Source and Destination. In the Source server preparation phase, you will perform a variety of server housekeeping tasks on the NetWare 4 or 5 server that hosts all your valuable files, volumes, and eDirectory information. Let's start with a closer look at the source-server preparation checklist: Use ConsoleOne to verify that you have the Supervisor right to the source server's file system and to the source server itself. Update the source server with the latest NetWare support pack. Updates are available at http://support.novell.com. (Conditional) If you are migrating data from NetWare 4, make sure the source server's volumes are running long-name space support on all volumes to be copied. To add long-name space support to a NetWare 4.11 or NetWare 4.2 volume, enter the following at the server console: LOAD LONG ADD NAME SPACE LONG TO volume name. Load DSREPAIR and run the following options: Back up eDirectory and all data.
Destination Server Preparation Next, you must prepare the destination server. This machine is the new computer that will receive the data from the source server. As such, it must be installed into a temporary, separate eDirectory tree. After that data is migrated from the source server to the destination server, the destination server reboots and the migration wizard modifies the destination server's AUTOEXEC.NCF file to include the source server's name and internal IPX number or server ID. You don't have to modify these manually. Let's continue with a closer look at the destination server preparation checklist: Use ConsoleOne to verify that you have the Supervisor right to the destination server's file system and to the server itself. Be sure you have created a temporary eDirectory tree with a temporary eDirectory tree name. The temporary name and temporary eDirectory tree name must not be the same as the source server's name or eDirectory tree name; otherwise, the destination server cannot assume the identity of the source server after the migration. During installation, create volumes on the destination server that are the same size as, or larger than, volumes on the source server. Volume names on the destination server must be the same as the volume names on the source server. If migrating from NetWare 4, install and configure IPX. IPX must be bound to the destination server for the migration to work. (You can remove IPX after completing the migration.) IP addresses for the source server are not migrated. Instead, you manually change them during migration. Install the destination server with the NetWare operating system that you are migrating to, and make sure you've installed the Pre-Migration installation type. In this case, you are probably migrating to NetWare 6. Make sure the destination server's time is equal to or later than the source server's time. This prevents critical time synchronization errors during migration.
TIP Migration Wizard migrates compressed volumes. If you are migrating compressed volumes to uncompressed volumes, Migration Wizard decompresses the volumes during migration. The decompression process is CPU and time intensive, so allow enough time to complete the operation. Make sure you have room on the uncompressed volume to accommodate the source volumes after they are decompressed.
Verify the Migration Client Finally, you'll need to verify the Novell Client version that is running on your migration client. The NetWare Migration Wizard can run from either a Windows 98 or Windows NT/2000 workstation. If you are using a Windows 98 workstation, be sure it is running the Novell Client for Windows 98 version 3.3 or higher. You can determine which version of the client software is running on your Windows 98 workstation by using any of these three methods: Hold down the Alt key while double-clicking the Windows 98 Network Neighborhood icon. Select the Novell Client, and then click Properties. Double-click the Network icon in the Windows 98 Control Panel. Select the Novell Client, and then click Properties. If you're running the Novell NetWare 6 Client, right-click the "N" icon near the right end of the Windows 98 toolbar, which is located at the bottom of your screen, by default. Select the Novell Client Properties option from the popup window that appears.
A Windows NT/2000 client must be running the Novell Client for Windows NT version 4.8 or higher. The client version should be listed on the title bar of the Login dialog box. If these methods don't work, you'll probably need to upgrade your client software. Refer to the first lesson of this chapter for detailed steps. That's all there is to it. Consider your three migration machines prepared. Now it's time to move on to the actual migration process also known as creating and implementing the Migration Project. |
