Server-to-Server Migration

This section is written as a guide to migrating from one server to a new server (box to box). The steps for this migration are described below, with references to previous sections, which include additional information.




	CAUTION: Carefully read all of this module BEFORE beginning any migration tasks. There is a significant risk of data loss if the migration steps are performed incorrectly.

Overview of the Client Utility MIGRATE.EXE

The Novell client migration utility MIGRATE.EXE is shipped on a floppy disk with this product. This utility runs on a client PC and its use is required in order to migrate the NetWare 3.1x bindery and trustee databases to NetWare 4.10 Directory Services (NDS). MIGRATE.EXE allows you to preserve your user environment (users and groups and their respective trustee assignments). Note, however, that remote printing-related configuration information is not preserved. Also, IP tunnelling information is maintained but needs to be copied manually to a different directory. Refer to the product README file for more information (/var/opt/netware4/README). Although hybrid user information is saved, it needs additional manipulation.

Possible Migration Paths

You can migrate to NetWare 4.1/9000 on HP-UX 10.10 or 10.20 on a new HP9000 server from one of the following NetWare/9000 environments on an existing HP9000 server (box):

- NetWare 3.11b/HP-UX 9.04

- NetWare 3.12/HP-UX 9.0x or 10.01 or 10.10 or 10.20

Performing the Server-to-Server Migration

This section describes the steps to migrate from one NetWare server to another NetWare server.

Preparation

Follow the steps below to prepare the server to server migration.

Back-up your NetWare 3.1x server.
Copy the migration utilities from the Client Utility Disk, which was shipped with NetWare 4.1/9000:
1. Insert the Client Utility Disk into a PC.
2. Create a directory on the PC for the migration utility (MIGRATE.EXE and related programs). For example:
  C:\MIGRATE
3. Change to that directory and, assuming the Client Utility Disk is in drive A:, unpack the migration utility onto the PC by entering:
  C:\MIGRATE>a:mig_unpk
4. From the PC, login to the NetWare 3.1x server as supervisor.
5. Ensure that a drive is mapped to the SYS volume of the server, then copy export.nw3 (a shell script) from the Client Utility Disk to the root of the SYS volume. For example, assuming drive F: is mapped to the SYS volume and the Client Utility Disk is in drive A:, enter:
  
  C:\>copy a:\export.nw3 f:\

Running the HP-UX Shell Script export.nw3




	NOTE: The information in this section also appears in the comments section at the beginning of the export.nw3 file.

export.nw3 is a shell script that programatically copies NetWare volumes and trustee, bindery and configuration data over the network, from the "old" NetWare/HP9000 Version 3.1x server to the "target" system that will be set up as the new NetWare/9000 Version 4.1x server.

The user netware and the group netware must exist on the target system before the script is run. In addition, if you are using the "hybrid user" feature of NetWare, or if any files or directories in any NetWare volumes are owned by a user or group other than netware, the HP-UX accounts for those users and their groups must also be set up in advance on the target. In general, any file or directory in a NetWare volume will lose its HP-UX user and group ownership attributes on the target system if the user and group do not exist on the target. The uids and gids MUST BE THE SAME on both systems for user and group ownership to be preserved (including the netware user and group).
In order for export.nw3 to work, the target system must be configured to accept rcp(1) and remsh(1) calls from the old system, in particular, there must be an entry for the old system in the target system's /.rhosts file. If the entry does not exist, edit /.rhosts and create it. The entry should consist simply of one line containing only the name of the old system, as returned by the hostname command on the old system. The name should not be preceded by spaces or any other characters. A more elaborate discussion of how this works can be found under hosts.equiv(4) in the HP-UX manual pages.
Edit export.nw3 by adding the target server's name (as returned by the hostname command on the target system) to the line- - -following the comments section - - -that begins with TARGET=. For example:
TARGET=hpsys12
In the directory containing export.nw3, execute the following, to ensure that the file is owned by root:
chown root:sys export.nw3
Turn off write permission for all but root:
chmod 644 export.nw3
Run the script by entering:
`which ksh` export.nw3
Note that the backwards single quotes (`) must be included in this command.

Install and Configure NetWare 4.1/9000

Install NetWare 4.1/9000 on the HP9000 Server to which you are migrating. Refer to Chapter 1 of this manual for specific details.
Verify NetWare 4.1/9000 installation. Refer to Chapter 1 of this manual for more information.
Activate the 4.1 License Codeword on the server. Refer to Chapter 1 of this manual for more information.
Complete basic configuration (Networks, Services, NDS) on the server. Refer to Chapter 1 of this manual.
Check that the configuration values for your LAN interface(s), which were migrated from your NetWare 3.1x/9000 server, are correct for the new NetWare 4.1/9000 system. Use SAM or nwcm to check the values for lan_<x>_ppa, lan_<x>_adapter and lan_<x>_frame_type.
Setting the names and addresses of the servers.
At this point, the old server's configuration data has been migrated to the new server. Hence, both servers currently have the same name and internal network number. This conflict must be resolved before the server-to-server migration can procede: server names and internal network numbers must be unique on the network. Consider the following:
Because of the complexities of name propagation in an NDS network, it is extremely difficult to change the name of a NetWare 4.1 server or tree, once it has gone on-line. Conversely, changing the name of a NetWare 3.1x server is straightforward, but, there could be administrative complications, in, for example, environments using login scripts with hard-coded server names. Therefore we strongly urge that you carefully decide now - - - particularly if your NetWare 3.1x server is going to remain in service - - - what the permanent working names of the two servers will be. Changing a NetWare server's internal network number is simpler; regardless of whether the server is on version 3.1x or 4.1, once the internal network number has been changed you need only restart the NetWare protocol stack.
If the new server is going to inherit the old server's name, use sconsole to change the name and internal network number of the old server and restart NetWare. Even if you are going to decommission the old server, it must have some other temporary or "dummy" name and internal network number for the duration of the migration process.
If you want to change the new server's name and internal network number, use SAM or the command-line utility nwcm:

nwcm -s server_name=new_server_name
nwcm -s ipx_internal_network=new_ipx_internal_network

Note that the format for new_ipx_internal_network is 0xNum, where Num is a hexadecimal number of 1 to 8 digits.
Note: Before completing this step, you should have a fairly complete plan for configuring your NDS tree. For assistance, refer to: Introduction to NetWare Directory Services.
Set the NDS Bindery Context on the new system such that it is identical to the value you intend to use for your Organization Name in dsinstall (in step 8, just below). Use SAM or nwcm:

nwcm -s ds_bindery_context="O=organization_name"

Note that the double quotes ("O=...") must be included in this command.
Start NetWare 4.1/9000:
startnps
startnw
Install NDS. Refer to Chapter 1, Step 8 in this manual.

Running the MIGRATE.EXE utility (Step 13)

The network_trash_folder is not used in NetWare 4.1/9000. Thus, to avoid unnecessary error messages when you migrate, remove this directory from the SYS volume of the 3.12 server.
To do so, enter:
cd sys_volume_path rm -fr network_trash_folder
Check that name and address conflicts have been resolved and that both the old and new servers are up.
Start NetWare on a PC. If it is attached to a NetWare 3.1x server, use the SLIST command (if attached to a NetWare 4.1 server use the NLIST SERVER command) to view a list of active NetWare servers. You should see both the old and new servers listed.
Ensure that on the PC you are attached as SUPERVISOR to both servers. This can be done with almost any combination of LOGIN, MAP or ATTACH commands. For example,
login old_server/supervisor /b
attach new_server/supervisor
For the password on new_server, use the same ADMIN password you specified during dsinstall.
Verify your connections with the WHOAMI command.
On the PC, change to the drive and directory where the MIGRATE.EXE program is located.
On the PC, start the MIGRATE utility by entering:
MIGRATE
On the PC, at the "Select the type of migration" window, select:
Across-the-Wire migration.
On the PC, at the "Select the source LAN type" window, select:
Netware 3.x
On the PC, at the "Select the destination LAN type" window, select:
Netware 4.x
On the PC, "Configure the migration utility:"
1. Set "Working directory" to whatever directory you want to use.
  To change the default, at the prompt "Working Directory," press:
  [Enter]
  A data-entry box appears with the heading "Specify the full working directory path." If necessary, use [Backspace] to erase the default entry and enter your desired directory, or you can use the cursor keys to navigate to a directory.
2. The setting for "Error/warning action" is optional. This parameter controls whether or not there will be pauses when Error/Warning messages are sent to the screen. Regardless of the setting, Errors and Warnings will be written to the file MIGxxx.RPT file in the working directory. MIGRATE.EXE will allow you to view this file when it completes.
On the PC, "Define the NetWare 3.x source server:"
1. At the "Server:" field, press [Enter] to view a list of servers. Select the name of the old server and press [Enter].
2. At the "Information to migrate:" field, press [Enter] to view a list of migratable items.
  Use the arrow keys and [F5] to select all items EXCEPT : "All information", "Data files" and "Print queues and print server." (Remote printer migration is not supported.) Press [Enter] when finished.
3. At the "Source volumes to migrate:" field, use the arrow keys and [F5] to select all the volumes on your 3.1x/9000 server. Press [Enter] when finished.
On the PC, "Define the Netware 4.x destination server:"
1. At the "Server:" field, press [Enter] for a list, highlight the new server, and press [Enter] to select the desired destination server.
2. At the "Volume destinations" field, press [Enter] to display the volumes. Use the arrow keys and [F5] to select all the volumes.
  NOTE: Press [F10] to accept selections, not [Enter] as in most other instances.
3. At the "Passwords" field, press [Enter] to select whether or not to assign random passwords. Old passwords cannot be migrated. Make your selection based on the following information.
  Assign Random Passwords: Each user will be given an encoded password. The network administrator will then have to manually assign a meaningful password to each user. The user can then change the password later (using SETPASS). This option provides good security, but is a lot of work for the administrator.
  Assign No Passwords: Each user account is migrated without a password. The administrator or the users can then set passwords as soon as possible after the new NetWare 4.1/9000 server is brought up.
On the PC, to begin migration to the Destination 4.1 Server, press [F10], select "Start migration" and press [Enter].
You may notice a warning flash by on the screen saying that the user SUPERVISOR already exists. You can ignore this.
After the migration has completed, the following message will appear:
"Migration from the source server to the destination server is complete.
Press <Enter> to continue."
You have now finished running MIGRATE.EXE.

Final Steps on the Server

Complete the steps below to finish the migration.

Run /opt/netware4/bin/migrate_ids. This utility ensures that the values for file ownership on the NetWare 4.1/9000 server are consistent with their original values from the NetWare 3.1x environment.
Verify NetWare 4.1/9000 operation on the server and client.