12.1 Prerequisites for Moving an NSS Volume with DFS

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

12.1.3 Preparing the Source Server and Volume

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.

  1. For OES 2015 or later, ensure that NCP Server is installed and running.

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

  2. Ensure OES Storage Management Services (SMS) is installed and running.

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

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

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

    2. At the terminal console prompt, enter the following command:

      smsconfig -u tsafs

    3. At the terminal console prompt, enter the following command:

      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 move 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 the volume is migrated back to the original source server node.

      IMPORTANT:Moving a shared volume is supported only on an OES 2 SP3 or later server.

  4. (Conditional) If the source volume is currently part of a shadow volume with 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 2018 SP3: Dynamic Storage Technology Administration Guide.

  5. (Conditional) 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 OES 2018 SP3: NSS File System Administration Guide for Linux.

  6. (Conditional) 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.

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

    1. In iManager, click Storage > Volumes.

      For instructions, see Section 8.1.3, Accessing Roles and Tasks in iManager.

    2. Select the source server to view a list of its NSS volumes.

    3. In the Volumes list, select the source NSS volume that you want to move, then wait until the page refreshes and displays information about the selected volume.

    4. Click Properties to view attributes for the selected volume.

  8. Ensure SLP is configured and running. To verify if SLP is running, run the following command:

    slptool findsrvs smdr.novell

    On running the above command destination server must also be displayed.

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

  2. For OES 2015 or later, ensure that NCP Server is installed and running.

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

  3. Ensure OES Storage Management Services (SMS) is installed and running.

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

  4. If you are moving from NetWare to OES 2015 or later, 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. (Conditional) If you are moving from an OES 2 SP3 or later target server, if the target volume is a shared volume, reload tsafs on the target server:

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

    2. At the terminal console prompt, enter the following command:

      smsconfig -u tsafs

    3. At the terminal console prompt, enter the following command:

      smsconfig -l tsafs --showclustervolumesonnode

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

      IMPORTANT:Moving a shared volume is supported only on an OES 2 SP3 or later server.

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

  7. Ensure that the destination server is registered with SLP for smdrd service and SLP is up and running.