Rehosting transitioned volumes to a different SVM

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.

• 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.
     Clustered Data ONTAP 8.3.2 man page: volume unmount - Unmount a volume
  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. Optional: Create the export policy.
     Clustered Data ONTAP 8.3.2 man page: vserver export-policy create - Create a rule set
  6. Update the export policy of the rehosted volume to a user-defined export policy.
     Clustered Data ONTAP 8.3.2 man page: volume modify - Modify volume attributes
  7. Mount the volume under the appropriate junction path in the destination SVM.
     Clustered Data ONTAP 8.3.2 man page: volume mount - Mount a volume on another volume with a junction-path
  8. Verify that the NFS service is running on the destination SVM.
     Clustered Data ONTAP 8.3.2 man page: vserver nfs status - Display the status of the NFS service of a Vserver
  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.
  Clustered Data ONTAP 8.3 File Access Management Guide for NFS
• Rehosting CIFS volumes
  1. Record information about the CIFS shares.
  2. Unmount the volume from the parent volume.
     Clustered Data ONTAP 8.3.2 man page: volume unmount - Unmount a volume
  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.
     Clustered Data ONTAP 8.3.2 man page: volume mount - Mount a volume on another volume with a junction-path
  6. Create CIFS shares for the rehosted volume.
     Clustered Data ONTAP 8.3.2 man page: vserver cifs share create - Create a CIFS share
  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.
  Clustered Data ONTAP 8.3 File Access Management Guide for CIFS
• Rehosting volumes in SnapMirror relationships
  1. Record the SnapMirror relationship type.
     Clustered Data ONTAP 8.3.2 man page: snapmirror show - Display a list of SnapMirror relationships
  2. From the destination cluster, delete the SnapMirror relationship.

     Clustered Data ONTAP 8.3.2 man page: snapmirror delete - Delete a SnapMirror relationship

     Important: 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:

     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.

     Clustered Data ONTAP 8.3.2 man page: snapmirror release - Remove source information for a SnapMirror relationship

  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.
     Clustered Data ONTAP 8.3.2 man page: vserver peer create - Create a new Vserver peer relationship
  7. Create the SnapMirror relationship between the source and destination volumes.

     Clustered Data ONTAP 8.3.2 man page: snapmirror create - Create a new SnapMirror relationship

     The rehosted volume can be the source or destination of the SnapMirror relationship.
  8. Resynchronize the data protection relationship.
     Clustered Data ONTAP 8.3.2 man page: snapmirror resync - Start a resynchronize operation
  Clustered Data ONTAP 8.3 Data Protection Guide