Skip to main content

Rehost a SAN volume

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

You can rehost a SAN volume that serves data through mapped LUNs. After re-creating the initiator group (igroup) in the destination SVM, volume rehost operation can automatically remap the volume at the same SVM.

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:

    • Antivirus policies

    • Volume efficiency policy

    • Quality of service (QoS) policies

    • Snapshot policies

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

  • There must be no active I/O on the volumes or LUNs.

  • You must have verified that the destination SVM does not have igroup of the same name but different initiators.

    If the igroup has the same name, then you must have renamed the igroup in either one of the SVMs (source or destination).

  • You must have enabled the force-unmap-luns option.

    • The default value of the force-unmap-luns option is false.

    • No warning or confirmation message is displayed when you set the force-unmap-luns option to true.

Steps

  1. Record LUN mapping information on target volume:

    lun mapping show volume volume vserver source_svm

    This is a precautionary step to avoid losing information about LUN mapping in case the volume rehost fails.

  2. Delete igroups associated with the target volume.

  3. Rehost the target volume to the destination SVM:

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

  4. Map LUNs on the target volume to appropriate igroups:

    • Volume rehost preserves LUNs on the target volume, however the LUNs remain unmapped.

    • Use the destination SVM port set while mapping LUNs.

    • If the auto-remap-luns option is set to true, the LUNs are mapped automatically after rehost.