In the migration tool file system GUI, Volume Information tab displays empty boxes for non-english directory names.This issue occurs if the corresponding language is not installed on the source server.To install fonts for non-english languages, run yast2 language, and select languages in the Secondary Languages pane. After installing required languages, restart the migration project.
Open files on the source server are not migrated. If files are open, they are not migrated because this causes data inconsistencies.
Close the files and then perform migration.
nbackup encountered files with the Execute-only bit set. By default, these files are not copied.
If you want to copy the Execute-only files, use the tsafs /ExcludeExecuteOnly=0 setting on the source NetWare server.
Source volumes or the target volumes are unavailable or are renamed during migration.
Do not rename volumes when migration is in progress. If migration stops because a volume is unavailable, ensure that the volume is properly activated and mounted, then restart the migration project.
If the ownership information is changed on migrating from NSS to NCP, make sure you LUM-enable the users that are migrated into the target eDirectory tree before you run the migfiles command.
If you LUM-enabled the users that were migrated into the target eDirectory tree and still don’t see the proper ownership information (for example, the owner is nobody as viewed in POSIX, or the server name as viewed by the Novell Client), try the following:
At the OES server terminal prompt, enter namcd cache_refresh.
Synchronize the eDirectory replicas by using DSREPAIR.
Enter nsscon /resetidcache.
To verify the information of the owner, enter:
ls -l /usr/novell/NCP1
There might be two admin users in the system (local admin user and eDirectory admin user). The failure was caused because the local admin user which does not have permission was trying to perform file system migration.
To resolve this issue, delete or rename the local admin user, then perform file system migration.
To resolve this issue, set the parameter tsamode to Linux in the /etc/opt/novell/sms/tsafs.conf file.
If the Novell Client fails, the volumes on the source server are not mapped. The file system migration does not depend on the Novell Client commands, but it uses nwmap to map the source volumes. The details of the error is logged in /var/opt/novell/migration/<project name>/log/filesystem.log.
To troubleshoot this issue, perform the following:
Verify the status of the Novell Client by entering the following command:
rcnovfsd status
If the service is running, restart the service by entering the following command:
rcnovfsd restart
or
If the service is not running, start the service by entering the following command:
rcnovfsd start
To configure the file system, select the file system and click Configure.
(Conditional) If the error is displayed again, verify the status of novell-xregd service by entering the following command:
rcnovell-xregd status
If the status is running, restart the service by entering the following command:
rcnovell-xregd restart
or
If the status is not running, start the service by entering the following command:
rcnovell-xregd start
Restart the Novell Client by entering the following command:
rcnovfsd restart
To configure the file system, select the file system and click Configure.
(Conditional) If the error is displayed after restarting novfsd and novell-xregd services, refer to the log file to verify if the Novell Client has failed to resolve the IP address.
If the IP address was not resolved, create a /etc/opt/novell/ncl/protocol.conf file and add the following line in it: Name_Resolution_Providers=NCP,SLP,DNS
Restart the Novell Client by entering the following command:
rcnovfsd restart
To configure the file system, select the file system then click Configure.
When you click Start in the main migration window, migration fails and you receive the error that no data sets are found.
Migration might fail if there is some problem during the setup and zapi is not loaded on the source server. To troubleshoot this issue, perform the following:
Verify that zapi is loaded on the source server by executing the following command:
lsmod | grep zapi
(Conditional) If zapi is displayed in the list then update the zapi.
(Conditional) If zapi is not displayed in the list, restart SMDR.
novell-smdrd restart
Click on Start, to start the migration.
The migtrustees command fails with a fatal error which is recorded in the filesystem.log file.
The migtrustees command takes input from the maptrustees.yaml file, which includes various attributes. Some special characters are included in the loginScript attribute of the maptrustees.yaml file which is not recognized by the migtrustees command causing failure in migration.
To troubleshoot this issue, perform the following steps:
Open the iManager page on the source server.
Click Users > Modify Users.
Select the username, which has special characters in the login script.
For example, if you see the error for cn=testuser,ou=users,o=novell in the filesystem.log file, select testuser from the user list.
Click General > loginScript.
Remove the special characters from the login script.
Click on apply then ok.
Remove the migtrustees.session, maptrustees.session and the maptrustees.yaml files from the /var/opt/novell/migration/<Project name>/fs/ folder of the target server.
This ensures that we re-execute the maptrustees command when continuing the migration process.
Click Start on the main Migration Tool window of the target server to continue migration.
The language pack is not installed on the target server, so the code page and the non-English characters are not displayed.
You need to install the language pack of the source server on the target server before starting the migration tool.
This issue occurs because the Is Cluster Resource option is not selected in Source Server Authentication or the cluster resource is down.
If the Is Cluster Resource option is not selected, select the option from Source Server Authentication, then reconfigure.
or
If the Is Cluster Resource option is selected and the cluster volumes are not displayed, verify the list of cluster volumes by executing the following command:
/opt/novell/sms/bin/smstool --list-cluster-volumes -R <resourceIP> -U <admin_credentials>
If files are open on the source server during synchronization, those files are not synchronized with the files on the target server. If trustees are deleted on the source server during or before synchronization, the trustees are not migrated. Ensure that you verify the following before synchronizing, then click Sync.
No application or user is accessing the source volumes that are being copied.
Select disable login in the file system GUI to restrict access to the source volumes.