Skip to main content

lun copy start

Start copying a LUN from one volume to another within a cluster

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

Description​

The lun copy start command initiates copying of a LUN from one volume to another. The destination volume can be located in the same Vserver as the source volume (intra-Vserver copy) or in a different Vserver (inter-Vserver).

Note
A cluster administrator must first create a Vserver peering relationship using vserver peer create before initiating an inter-Vserver LUN copy operation.

Parameters​

-vserver <Vserver Name> - Destination Vserver Name
Specifies the name of the Vserver that will host the new LUN.
| -destination-path <path> - Destination Path
Specifies the full path to the new LUN, in the format /vol/<volume>[/<qtree>]/<lun>.
-source-path <path>} - Source Path
Specifies the full path to the source LUN, in the format /vol/<volume>[/.snapshot/<snapshot>][/<qtree>]/<lun>.
[-source-vserver <vserver name>] - Source Vserver Name
Optionally specifies the name of the Vserver hosting the LUN to be copied.

If this parameter is not specified, it is assumed that an intra-Vserver copy operation is being initiated. The source volume is expected to be in the same Vserver as the destination volume.

[-promote-early [true]] - Promote Early
Optionally specifies that the destination LUN needs to be promoted early.

If the destination is promoted early, the new LUN will be visible immediately. However, Snapshot copies of the volume containing the new LUN cannot be taken until the LUN copy operation reaches 'Moving Data' status.

If the destination is promoted late, the new LUN will be visible only after it has been fully framed. However, the LUN copy job will not block the creation of Snapshot copies of the volume containing the new LUN.

If this parameter is not specified, the destination LUN will be promoted late.

[-max-throughput {<integer>[KB|MB|GB|TB|PB]}] - Maximum Transfer Rate (per sec)
Optionally specifies the maximum amount of data, in bytes, that can be transferred per second in support of this operation. This mechanism can be used to throttle a transfer, to reduce its impact on the performance of the source and destination nodes.

If this parameter is not specified, throttling is not applied to the data transfer.

Note
The specified value will be rounded up to the nearest megabyte.

Examples​

cluster1::> lun copy start -vserver vs2 -destination-path /vol/vol2/lun2 -source-vserver vs1 -source-path /vol/vol1/lun1
Starts an inter-Vserver copy of LUN lun1 from volume vol1 in Vserver vs1 to lun2 on volume vol2 in Vserver vs2.
cluster1::> lun copy start -vserver vs1 -destination-path /vol/vol2/lun2 -source-path /vol/vol1/lun1
Starts an intra-Vserver copy of LUN lun1 from volume vol1 in Vserver vs1 to lun2 on volume vol2 in Vserver vs1.
cluster1::> lun copy start -vserver vs1 -destination-path /vol/vol2/lun2 -source-path /vol/vol1/.snapshot/snap1/lun1
Related reference