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, and so forth.) 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 are 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.
Shut down any applications, products, or services (virus scan software, backup software, and so forth.) running on the server to be migrated.
Ensure that the server is running OES 1, OES 2, or OES 11 with all the available patches in the channel.
Ensure that Storage Management Services (SMS) and NetWare Core Protocol (NCP) is running on the server.
Ensure that source volumes on OES 1, OES 2 Linux, or OES11 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, OES 2, or OES 11 server, 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 11 SP3.
Services to be migrated must be installed and configured on the target server.
The following additional prerequisites must be met for NSS and NCP target volumes:
Using Migration GUI, if you have configured the file system and for some reason the mount point of NSS volumes change, you must reconfigure the paths for the file system.
Create the NSS volumes to which you will migrate 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.
Using CLI, if you want to use the CASA secret store to store user names and passwords during migration (via the --use-casa option), ensure that the following RPM is installed on the OES server:
CASA-1.7.XXX.rpm
Restart the CASA daemon by entering the following command:
/etc/init.d/micasad restart
Create NCP volumes to which you will migrate the data.
Ensure that the user performing the migration has read/write/access rights to the POSIX path that corresponds to the NCP volume.
Although data is successfully migrated to the clustered NCP target volumes, trustee migration is not supported.