There are multiple conditions that result in a job failure:
The Move or Split job failed for an unspecified reason. This failure state is unlikely because most failures identify a specific error.
The Move or Split job failed because the Novell Storage Management Services (SMS) could not be started. The Volume Manager uses SMS to move data by backing it up from the original volume and immediately restoring it to the new volume.
Make sure that SMS is installed and loaded on the original and destination servers, then try again.
The Move or Split job failed because a read error occurred while SMS was backing up files from the original volume. The Volume Manager uses SMS to move data by backing it up from the original volume and immediately restoring it to the new volume.
This error does not occur if the file that SMS is trying to read is merely open. DFS tracks files that are open when SMS attempts to back them up and tries again to back them up later in the process.
The Move or Split job failed because a write error occurred while SMS was restoring files to the new volume. The Volume Manager uses SMS to move data by backing it up from the original volume and immediately restoring it to the new volume.
To avoid this problem, make sure the new volume has sufficient space allocated to contain the data you intend to move to it.
The Move or Split job failed because the specified original server has a version of NSS that does not support Move and Split. For information about supported server platforms for Moves, see Section 9.1.2, Supported Combinations for Moving Volumes. For information about supported server platforms for Splits, see Section 9.1.3, Supported Combinations for Splitting Volumes.
The Move or Split job failed because the specified target server has a version of NSS that does not support Move and Split. For information about supported server platforms for Moves, see Section 9.1.2, Supported Combinations for Moving Volumes. For information about supported server platforms for Splits, see Section 9.1.3, Supported Combinations for Splitting Volumes.
The Move or Split job failed because a log file cannot be created or DFS cannot write to it. DFS tracks files that are open when SMS attempts to back them up and tries again to back them up later in the process. The process fails because it needs the log file to identify which files to retry to move.
The Move or Split failed because the supplied user name and password were invalid.
To avoid this problem, make sure you have the necessary rights and permissions to move files on the original volume and the new volume.
If the volumes on different servers, the administrator username and password you use when you log in to iManager to create the job must be valid on both servers.
By default, usernames are case sensitive on Linux, but they are case insensitive on NetWare. Login fails if you are using the what appears to be the same username, but it is treated differently on the two platforms. To avoid this problem, make sure to create usernames in lowercase.
The server where the original volume exists is not contained in a DFS Management context. Move and Split are DFS operations, and require the original and destination servers to be in the same DFS Management context.
Define a management context that includes both servers, allow time for the VLDB to be built, then try again.
The original server and the new server specified in a Move or Split job are in different DFS Management contexts. This is not allowed.
Define a management context that includes both servers, allow time for the VLDB to be built, then try again.