Skip to main content

volume rehost

Contributors
Suggest changes
PDFs

Rehost a volume from one Vserver into another Vserver

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The volume rehost command rehosts a volume from source Vserver onto destination Vserver. The volume name must be unique among the other volumes on the destination Vserver. This command is not supported in a MetroCluster configuration.

Parameters

-vserver <vserver name> - Source Vserver name

This specifies the Vserver on which the volume is located.

-volume <volume name> - Target volume name

This specifies the volume that is to be rehosted.

-destination-vserver <vserver name> - Destination Vserver name

This specifies the destination Vserver where the volume must be located post rehost operation.

{ [-force-unmap-luns {true|false}] - Unmap LUNs in volume

This specifies whether the rehost operation should unmap LUNs present on volume. The default setting is false (the rehost operation shall not unmap LUNs). When set to true, the command will unmap all mapped LUNs on the volume.

| [-auto-remap-luns {true|false}] - Automatic Remap of LUNs }

This specifies whether the rehost operation should perform LUN mapping operation at the destination Vserver for the LUNs mapped on the volume at the source Vserver. The default setting is false (the rehost operation shall not map LUNs at the destination Vserver). When set to true, at the destination Vserver the command will create initiators groups along with the initiators (if present) with same name as that of source Vserver. Then the LUNs on the volume are mapped to initiator groups at the destination Vserver as mapped in source Vserver.

[-key-manager-attribute <text>] - Optional CRN

This optional parameter specifies an additional key manager attribute that should be an identifier-value pair separated by '=', ex. CRN=my-unique-value

The following identifiers are currently supported:

  • CRN

Examples

The following example rehosts a volume named vol3 on Vserver named vs1 to a destination Vserver named vs2:

cluster::> volume rehost -vserver vs1 -volume vol3 -destination-vserver vs2