13.1 Prerequisites for Splitting an NSS Volume with DFS

13.1.1 Planning the Split Volume Job

Make sure you meet the prerequisites and guidelines in the following sections of Section 9.0, Planning for DFS:

13.1.2 Preparing the DFS Management Context

  1. If one does not already exist, create a DFS management context that contains both the source and destination servers.

    For instructions, see Section 10.1, Creating a DFS Management Context.

  2. Make sure the VLDB service for the management context is synchronized and running.

    For instructions, see Section 10.7, Monitoring the Health of the VLDB Service.

  3. If necessary, start or activate the VLDB service.

    For instructions, see Section 10.4, Starting or Activating the VLDB Service.

13.1.3 Preparing the Source Server and Directory

If the NSS volume is an encrypted volume, you should not use DFS to split 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.

  1. For OES 2 Linux, make sure NCP Server is installed and running.

    For instructions, see the OES 2 SP3: NCP Server for Linux Administration Guide.

  2. Make sure Novell Storage Management Services (SMS) is installed and running.

    For instructions, see Installing and Configuring SMS in the OES 2 SP3: Storage Management Services Administration Guide for Linux.

  3. (Conditional) For an OES 2 SP3 source server, if the source volume is a shared volume, reload the tsafs on the source server.

    1. Open a terminal console, then log in as the root user.

    2. At the terminal console prompt, enter

      smsconfig -u tsafs

    3. At the terminal console prompt, enter

      smsconfig -l tsafs --showclustervolumesonnode

      The DFS Volume Manager treats the shared source volume as a local or unshared volume on the source server. During the split job, if the source volume is migrated to another node, the DFS Volume Manager sets the status of the job to Scheduled and continues the job only when it is migrated back to the original source server node.

      IMPORTANT:Splitting a shared volume is supported only on an OES 2 SP3 server.

  4. (Conditional) 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 split the volume.

    For information about Dynamic Storage Technology, see the OES 2 SP3: Dynamic Storage Technology Administration Guide.

  5. (Conditional) If there are deleted files that you want to keep in the directory you are splitting, salvage those deleted files before you define the split job.

    For information about salvaging deleted files, see Salvaging or Purging Deleted Files with Other Tools in the OES 2 SP3: NSS File System Administration Guide for Linux.

  6. (Conditional) If you are splitting the directory 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.

  7. Set explicit trustees and trustee rights on the directory so they can be transferred to the junction when the split job is complete.

    Users must have Read and File Scan rights to the directory. Inherited trustees and trustee rights are not automatically transferred to the target volume.

    IMPORTANT:You must set rights on the target volume or directory after the split is complete.

13.1.4 Preparing the Destination Server

  1. 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.

  2. For OES 2 Linux, make sure NCP Server is installed and running.

    For instructions, see the OES 2 SP3: NCP Server for Linux Administration Guide.

  3. Make sure Novell Storage Management Services (SMS) is installed and running.

    For instructions, see Installing and Configuring SMS in the OES 2 SP3: Storage Management Services Administration Guide for Linux.

  4. If you are splitting from NetWare to OES 2 Linux, configure the SMS TSAFS mode to dual.

    1. Open a terminal console, then log in as the root user.

    2. 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.

  5. If you are splitting 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.