Rehosting transitioned volumes to a different SVM

Contributors netapp-ivanad ntap-bmegan Download PDF of this page

Volume rehost enables you to migrate a transitioned volume from one SVM to another SVM without data copy. The rehost operation enables you to consolidate all volumes that have FC LUNs to a single SVM, thereby preserving the 7-Mode single-system image (SSI) semantics. You can also rehost transitioned NAS volumes.

  • The volume that you want to rehost must be online.

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

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

    Rehosting is a disruptive operation.

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

  • Volume and qtree export policies

  • Antivirus policies

  • Volume efficiency policy

  • Quality of Service (QoS) policies

  • Snapshot policies

  • Quota rules

  • CIFS shares

  • igroups associated with a portset

Steps
  • Rehosting FC and iSCSI volumes

    1. Switch to the advanced privilege level:
      set -privilege advanced

    2. Rehost the volume on the destination SVM:

      If you want to…​ Run the following command…​

      Unmap the LUNs after rehosting

      volume rehost -vserver source_svm -volume vol_name -destination-vserver destination_svm -force–unmap-luns true

      Remap the LUNs to the same igroups after rehosting

      volume rehost -vserver source_svm -volume vol_name -destination-vserver destination_svm -auto-remap-luns true

  • Rehosting NFS volumes

    1. Record information about the NFS export policies.

    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 vol_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:
      vserver nfs status

    9. Resume NFS access to the rehosted volume.

      Because the volume access path (LIFs and junction path) has undergone changes, you must update the NFS client credentials and LIF configurations to reflect the destination SVM LIFs.

  • Rehosting CIFS volumes

    1. Record information about the CIFS shares.

    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 vol_name -destination-vserver destination_svm

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

    6. Create CIFS shares for the rehosted volume:
      vserver cifs share create

    7. If the DNS domains differ between the source and destination SVMs, create new users and groups.

    8. Update the CIFS client with the new destination SVM LIFs and junction path to the rehosted volume.

  • Rehosting volumes in SnapMirror relationships

    1. Record the SnapMirror relationship type:
      snapmirror show

    2. From the destination cluster, delete the SnapMirror relationship:
      snapmirror delete

      You must not break the SnapMirror relationship; otherwise, the data protection capability of the destination volume is lost and the relationship cannot be reestablished after the rehosting operation.
    3. From the source cluster, release the SnapMirror relationship information:
      snapmirror release

      You set the -relationship-info-only parameter to true so that the Snapshot copies are not deleted and only the source relationship information is removed.

    4. Switch to the advanced privilege level:
      set -privilege advanced

    5. Rehost the volume on the destination SVM:
      volume rehost -vserver source_svm -volume vol_name -destination-vserver destination_svm

    6. Create the SVM peer relationship between the source and destination SVMs:
      vserver peer create

    7. Create the SnapMirror relationship between the source and destination volumes:
      snapmirror create

      The rehosted volume can be the source or destination of the SnapMirror relationship.

    8. Resynchronize the data protection relationship:
      snapmirror resync

You must manually create the autovolume workloads for the rehosted volumes by performing the following steps:

  1. Create a user-defined policy group for the SVM:

    qos policy-group create -vserver destination-vserver -policy-group policy-group-name

  2. Assign the QoS policy group to the rehosted volume:

    volume modify -vserver destination-vserver -volume rehosted-volume -qos-policy-group policy-group-name

You must manually reconfigure the policies and the associated rules on the rehosted volume.

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

Related information