Make sure you meet the prerequisites and guidelines in the following sections of Section 8.0, Planning for DFS:
If one does not already exist, create a DFS management context that contains both the source and destination servers.
For instructions, see Section 9.1, Creating a DFS Management Context.
Make sure the VLDB service for the management context is synchronized and running.
For instructions, see Section 9.7, Monitoring the Health of the VLDB Service.
If necessary, start or activate the VLDB service.
For instructions, see Section 9.4, Starting or Activating the VLDB Service.
If the NSS volume is an encrypted volume, you should not use DFS to move the volume. You cannot create an encrypted volume as the destination volume because that capability is limited to volumes created in NSSMU. Thus, the destination volume would be unencrypted.
For OES 2 Linux, make sure NCP™ Server is installed and running.
For instructions, see the OES 2 SP2: NCP Server for Linux Administration Guide.
NOTE:NCP Server is installed and running by default on a NetWare® server.
Make sure Novell Storage Management Services™ (SMS) is installed and running.
For instructions, see Installing and Configuring SMS
in the NW 6.5 SP8: Storage Management Services Administration Guide.
If the source volume is currently part of a shadow volume with Novell Dynamic Storage Technology, you must remove the shadow before you can use DFS to move the volume.
For information about Dynamic Storage Technology, see the OES 2 SP2: Dynamic Storage Technology Administration Guide.
If there are deleted files that you want to keep on the volume, salvage those deleted files before you define the move job.
For information about salvaging deleted files, see Salvaging or Purging Deleted Files with Other Tools
in the NW 6.5 SP8: NSS File System Administration Guide.
If you are moving the volume to a pool on a different server, make sure that the administrator username and password you use to log in to iManager are valid on both servers.
View the attribute settings for the source NSS volume so that you have the information you need to set the same settings for the destination volume.
In iManager, click .
For instructions, see Section 7.1.3, Accessing Roles and Tasks in iManager.
Select the source server to view a list of its NSS volumes.
In the list, select the source NSS volume that you want to move, then wait until the page refreshes and displays information about the selected volume.
Click to view attributes for the selected volume.
Make sure the destination server contains a disk with sufficient free space to create the destination volume.
You must have unpartitioned free space available for this volume on the destination server. For Linux, the free space must be on an unpartitioned device or on a device that is managed by the Enterprise Volume Management System (EVMS) volume manager.
For OES 2 Linux, make sure NCP Server is installed and running.
For instructions, see the OES 2 SP2: NCP Server for Linux Administration Guide.
NOTE:NCP Server is installed and running by default on a NetWare server.
Make sure Novell Storage Management Services (SMS) is installed and running.
For instructions, see Installing and Configuring SMS
in the NW 6.5 SP8: Storage Management Services Administration Guide.
If you are moving from NetWare to OES 2 Linux, configure the SMS TSAFS mode to dual.
Open a terminal console, then log in as the root user.
At a terminal console prompt, enter
smsconfig -l tsafs --tsaMode=dual
IMPORTANT:After the move job is completed, make sure to reset the TSAFS mode to linux.
If you are moving the volume to a pool on a different server, make sure that the administrator username and password you use to log in to iManager are valid on both servers.