Skip to main content

Rehost an NFS volume

Contributors netapp-dbagwell dmp-netapp netapp-ahibbard netapp-aherbin
PDFs

You can rehost a volume that serves data using the NFS protocol. To allow clients to continue accessing the data after the rehosting operation, you must associate the volume with the export policy of the SVM as well as manually configure the policies and associated rules.

About this task

  • Rehosting is a disruptive operation.

  • If the rehosting operation fails, you might need to reconfigure the volume policies and the associated rules on the source volume.

  • Beginning in ONTAP 9.8, rehosting a volume with NetApp Volume Encryption (NVE) is supported. If you are using an onboard key manager, the encrypted metadata will be modified during the rehost operation. User data is not changed.

    If you are using ONTAP 9.8 or early, you must unencrypt the volume before performing the rehost operation.

  • After the rehost operation, the following volume policies, policy rules, and configurations are lost from the source volume, and must be manually reconfigured on the rehosted volume:

    • Volume and qtree export policies

    • Antivirus policies

    • Volume efficiency policy

    • Quality of service (QoS) policies

    • Snapshot policies

    • Quota rules

    • ns-switch and name services configuration export policy and rules

    • User and group IDs

Before you begin

  • The volume must be online.

  • Volume management operations, such as volume moves or LUN moves, must not be running.

  • Data access to the volume that is being rehosted must be stopped.

  • The ns-switch and name services configuration of the target SVM must be configured to support data access of the rehosting volume.

  • The user ID and group ID of the volume must be either available in the target SVM or changed on the hosting volume.

Steps

  1. Record information about the NFS export policies to avoid losing information on NFS policies in case volume rehost operation fails.

  2. Unmount the volume from the parent volume:

    volume unmount

  3. Switch to the advanced privilege level:

    set -privilege advanced

  4. Rehost the volume on the destination SVM:

    volume rehost -vserver source_svm -volume volume_name -destination-vserver destination_svm

    The default export policy of the destination SVM is applied to the rehosted volume.

  5. Create the export policy:

    vserver export-policy create

  6. Update the export policy of the rehosted volume to a user-defined export policy:

    volume modify

  7. Mount the volume under the appropriate junction path in the destination SVM:

    volume mount

  8. Verify that the NFS service is running on the destination SVM.

  9. Resume NFS access to the rehosted volume.

  10. Update the NFS client credentials and LIF configurations to reflect the destination SVM LIFs.

    This is because the volume access path (LIFs and junction path) has undergone changes.

After you finish

You must manually reconfigure the policies and the associated rules on the rehosted volume. See NFS configuration for more information.