9.6 Guidelines for Moving or Splitting NSS Volumes

The Move Volume and Split Volume 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):

The destination location for a move or split is a newly created NSS volume on one of the following server platforms (or later versions):

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 Logical Volume Manager (NLVM).

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 Move Volume or Split Volume 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 NetIQ 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 23.4: NCP Server for Linux Administration Guide.

OES Storage Management Services (SMS) must be installed and running. 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 Move Volume job, the trustee access rights for the original volume are transferred automatically to the target volume.

For a Split Volume job, the implicit rights on the directory being split are moved to the target volume.