Rehosting SAN volumes
You can rehost volumes that have mapped LUNs. After re-creating the initiator group (igroup) in the destination SVM, volume rehost can automatically remap the volume on the same SVM.
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 .
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.
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