volume move modify
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
Modify parameters for a running volume move operation
Availability: This command is available to cluster administrators at the advanced privilege level.
Description
The volume move modify
command modifies the parameters used by the volume move operation in progress. These modified values can be verified by invoking the volume move show command. The volume move operation will use the modified cutover parameters in its next cutover attempt. Note that the modifications to the job are not applied if the move is in the "finishing" state. This command is not supported.
Parameters
-vserver <vserver name>
- Vserver Name-
This specifies the Vserver on which the volume is located.
-volume <volume name>
- Volume Name-
This specifies the name of the volume being moved.
[-cutover-action {abort_on_failure|defer_on_failure|force|wait|retry_on_failure}]
- Specified Action For Cutover (privilege: advanced)-
Specifies the action to be taken for cutover. If the effective cluster version is Data ONTAP 8.3 and later, the default is
retry_on_failure
; otherwise the default isdefer_on_failure
. If theabort_on_failure
action is specified, the job will try to cutover until cutover attempts are exhausted. If it fails to cutover, it will cleanup and end the operation. If thedefer_on_failure
action is specified, the job will try to cutover until the cutover attempts are exhausted. If it fails to cutover, it will move into the "cutover_hard_deferred" state. The volume move job waits for a volume move trigger-cutover command to restart the cutover process. If theforce
action is specified, the job will try to cutover until the cutover attempts are exhausted and force the cutover at the expense of disrupting the clients. If thewait
action is specified, when the job hits the decision point, it will not go into cutover automatically, instead it will wait for a volume move trigger-cutover command as the signal to try the cutover. [-cutover-window <integer>]
- Specified Cutover Time Window (privilege: advanced)-
This specifies the time interval in seconds to completely cutover operations from the original volume to the moved volume. The default value is 30 seconds. The range for valid input is from 30 to 300 seconds, inclusive.
[-enforce-network-throttling {true|false}]
- Enforce Replication Engine Node Level Network Throttling (privilege: advanced)-
This specifies whether this move should enforce replication engine node level network throttling. If this parameter is specified with
true
, the move will be throttled by the replication engine. The default isfalse
.
Examples
The following example modifies the parameters for volume move operation on volume vol2.
cluster1::*> volume move show -vserver vs0 -volume vol2 Vserver Name: vs0 Volume Name: vol2 Actual Completion Time: - Bytes Remaining: 172KB Specified Action For Cutover: wait Specified Cutover Time Window: 40 Time Cutover was Triggered: - Time Cutover was last triggered: - Destination Aggregate: node_1_aggr1 Destination Node: node_1 Detailed Status: Cutover Deferred, Waiting for user intervention(69.79MB Sent)::Volume move job preparing transfer Estimated Time of Completion: - Job ID: 105 Managing Node: node-2 Percentage Complete: 50% Move Phase: cutover_hard_deferred Estimated Remaining Duration: - Replication Throughput: - Duration of Move: 1 days 00:04 Source Aggregate: node_2_aggr1 Source Node: node_2 Start Time of Move: Sun Sep 18 16:40:37 2011 Move State: alert cluster1::*> volume move modify -vserver vs0 -volume vol2 -cutover-action abort_on_failure -cutover-window 50 cluster1::*> volume move show -vserver vs0 -volume vol2 Vserver Name: vs0 Volume Name: vol2 Actual Completion Time: - Bytes Remaining: 172KB Specified Action For Cutover: abort_on_failure Specified Cutover Time Window: 50 Time Cutover was Triggered: - Time Cutover was last triggered: - Destination Aggregate: node_1_aggr1 Destination Node: node_1 Detailed Status: Cutover Deferred, Waiting for user intervention(69.79MB Sent)::Volume move job preparing transfer Estimated Time of Completion: - Job ID: 106 Managing Node: node-2 Percentage Complete: 50% Move Phase: cutover_hard_deferred Estimated Remaining Duration: - Replication Throughput: - Duration of Move: 1 days 00:05 Source Aggregate: node_2_aggr1 Source Node: node_2 Start Time of Move: Sun Sep 18 16:40:37 2011 Move State: alert
The following example shows command failed to modify on vol1 as volume move operation is completed.
cluster1::*> volume move show -vserver vs0 -volume vol1 Vserver Name: vs0 Volume Name: vol1 Actual Completion Time: Sun Sep 18 16:34:27 2011 Bytes Remaining: 172KB Specified Action For Cutover: wait Specified Cutover Time Window: 30 Time Cutover was Triggered: - Time Cutover was last triggered: - Destination Aggregate: node_1_aggr1 Destination Node: node_1 Detailed Status: Volume move failed because of a job restart Estimated Time of Completion: - Job ID: 108 Managing Node: node-2 Percentage Complete: - Move Phase: failed Estimated Remaining Duration: - Replication Throughput: - Duration of Move: 15 days 08:07 Source Aggregate: node_2_aggr1 Source Node: node_2 Start Time of Move: Sat Sep 03 08:27:06 2011 Move State: failed cluster1::*> volume move modify -vserver vs0 -volume vol1 -cutover-action abort_on_failure -cutover-window 40 Error: command failed: There is no volume move operation running on the specified volume.