To prepare your network for file system migration, complete the tasks in the following sections:
Shut down any applications, products, or services (virus scan software, backup software, etc.) running on the server to be migrated.
Ensure that the latest version of Storage Management Services (SMS) is running on the source NetWare server.
SMS updates can be downloaded from the Novell Downloads Web site.
When migrating data from a Traditional NetWare volume, ensure that the NPM files for NFS and the NFS name space is loaded on the Traditional NetWare Volumes.
Although data on the source server is not deleted as part of the migration, we recommend that you back up your data.
(Conditional) For NetWare 6.0 server, you need to extract tsafs.nlm and smsut.nlm from the latest tsa5up patch, shipped for NetWare 6.5 and load it on the NetWare 6.0 server.
Shut down any applications, products, or services (virus scan software, backup software, etc.) running on the server to be migrated.
Ensure that the server is running OES 1 SP2 or OES 2 with all the available patches in the channel.
Ensure that the latest version of Storage Management Services (SMS) is running on the server.
Ensure that the latest version of NetWare Core Protocol (NCP) is installed on the server.
Ensure that source volumes on OES 1 or OES 2 Linux servers are NSS volumes, NCP volumes, or POSIX volumes.
NOTE:The Migration Tool GUI does not support POSIX file system migration. Create an NCP volume with the POSIX path that you want to migrate, then migrate the NCP volume.
To migrate data from NCP volumes on OES 1 server, ensure that you have done the following:
Install the Novell Client 2.0 SP2 for Linux
Restart SMS by running the following command:
rcnovell-smdrd restart
Ensure that the user performing migration has read/write/access rights to back up the files on the NCP volume.
To perform migration, the user must have read/write/access permissions to the source server
Ensure that the server is running OES 2 SP3.
Services to be migrated must be installed and configured on the target server.
If the source server is running NetWare 5.1 SP7 and your data contains extended ASCII or Unicode characters, add the following setting to the /etc/opt/novell/sms/tsafs.conf file of the target server:
useCodeSet=xxx
For xxx, substitute the code page value set on the NetWare server. For example, the default code page is 437. (Alternate forms include CP437, CSPC8CODEPAGE437, and IBM437).
Restart SMS by running the following command:
rcnovell-smdrd restart
The following additional prerequisites must be met for NSS and NCP target volumes:
You must reconfigure file system options, if NSS volumes are remounted to a different mount point.
Use the Novell Storage Services Management Utility (nssmu) or iManager to create the NSS volumes to which you will be migrating the data. Ensure that you allocate sufficient space for the volume to hold all of the source data.
Ensure that the target volumes have similar properties to the source volumes. For example, if compression is turned on for the source volume, turn on compression for the target volume as well. The same applies to user quotas and other NSS features.
If you want to use the CASA secret store to store usernames and passwords during the migration (via the --use-casa option), ensure that the following RPM is installed on the OES 2 Linux server:
CASA-1.7-xxx.i586.rpm
Restart the CASA daemon by entering the following command:
/etc/init.d/micasad restart
Use the NCP Server Console utility (ncpcon) to create the NCP volumes.
Ensure that the user performing the migration has read/write/access rights to the POSIX path that corresponds to the NCP volume.