Use the guidelines in this section when planning to use DFS to move or split NSS volumes.
The and tasks are available only for NSS volumes. Both the original and destination volumes are NSS.
The source volume must be an NSS data volume on one of the following server platforms (or later versions):
OES 2 Linux
NetWare 6.5 SP8
The destination location for a move or split is a newly created NSS volume on one of the following server platforms (or later versions):
OES 2 Linux
NetWare 6.5 SP8
The destination NSS volume is typically in a different pool on the same or different server.
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.
The destination volume should be configured with the same volume attributes as the original volume. Review the properties for the original volume before you begin a move or split, and note which attributes need to be set. Specifically, the compression attribute must match.
When moving or splitting a volume to a pool on a different server, the administrator username and password must be valid on both servers. Otherwise, the or job fails.
Deleted files are not relocated, so make sure to salvage any deleted files that you want to keep before you begin.
Users can continue to access data on the source volume during the move or split process.
The move or split process tracks which files change after they are copied, so files can be accessed while it is running. The job may reach a point where it is necessary for you to disconnect users in order to allow the job to finish, but not until it has at least attempted to copy all files multiple times.
You cannot move or split to an existing volume. Data is moved or split to the root of a newly created NSS volume that you configure when you define the move or split job.
The original and destination servers must be in the same DFS management context, so you cannot move or split across trees. The DFS management context is necessary even if you are moving the volume to a different pool on the same server.
If a DFS management context does not exist, you must create a DFS management context at an O or OU class level in the Novell eDirectory tree that contains both the source and destination servers. For instructions, see Section 10.1, Creating a DFS Management Context.
The VLDB service must be enabled and running in the DFS management context. For information, see Section 10.4, Starting or Activating the VLDB Service.
NCP Server must be running when you set up the move or split job and remain running until the job is completed.
If you are using CIFS/Samba options for users, make sure that NCP Server is up and running before you define the move or split job. It is not required that CIFS/Samba users be configured as NCP users during or after the move or split is completed.
For information about how to install and configure NCP Server on Linux, see Installing and Configuring NCP Server for Linux
in the OES 2 SP3: NCP Server for Linux Administration Guide.
Novell Storage Management Services (SMS) must be installed and running. On OES 2 Linux, the NetWare Emulation Mode (--tsaMode) for TSAFS must be set to dual when moving NSS volumes from NetWare to Linux. The default setting is linux. For instructions, see Configuring SMS.
For a job, the trustee access rights for the original volume are transferred automatically to the target volume.
For a job, the implicit rights on the directory being split are moved to the target volume.
If you use the Novell Distributed File Services Volume Move operation to move a volume that has been upgraded to the new media format for hardlinks, consider the following guidelines:
Before you create the DFS Move Volume job, make sure that NSS is set so that the new target volume is automatically created with the upgraded media format for enhanced hard links. For information and command options, see Upgrading the Media Format Automatically for New NSS Volumes
in the OES 2 SP3: NSS File System Administration Guide for Linux.
If you moved the volume without enabling the new media format, you must upgrade the volume to the new media format after the move completes successfully. For information and command options, see Upgrading the Media Format for Existing NSS Volumes
in the OES 2 SP3: NSS File System Administration Guide for Linux.
In the initial release of OES 2, the Move Volume Wizard does not have an option to enable the Hard Links attribute for the new target volume. After the move is completed and the media format is upgraded for enhanced hard links support, you must manually enable the Hard Links attribute. For instructions, see Enabling or Disabling the Hard Links Attribute
in the OES 2 SP3: NSS File System Administration Guide for Linux.
For OES 2 SP2 and earlier versions, perform the move/split only from an active node and only for unshared volumes. DFS supports Move and Split operations only from one unshared volume to another unshared volume in a cluster scenario. The Move and Split operations among shared volumes or from a shared or unshared volume to another unshared or shared volume do not work.
For OES 2 SP3 and later versions, perform the move/split only from an active node. DFS supports Move and Split operations from a shared or unshared volume to an unshared or shared volume in a cluster scenario.
Do not attempt to use the or tasks on a volume that is the primary or secondary storage area in a Novell Dynamic Storage Technology shadow volume.
If the NSS volume is a part of a shadow volume, you must force the data to either the primary or secondary NSS volume in that relationship. After all the data is on a single volume, remove the shadow volume relationship. Then you can move the data on the volume using DFS.
For more information about using DFS with DST, see Section 9.8, Guidelines for Using DFS and Novell Dynamic Storage Technology.