使用选项Wait to cutover时、卷移动的具体操作是什么？

最后更新
另存为PDF

Views:: 23

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: core

Last Updated:

适用场景

ONTAP 9

问题解答

问题1. 使用选项wait 进行转换、按如下所示实施卷移动操作、完成到 cutover_hard_deferred 阶段后、源卷上的新数据是否会继续复制到目标卷？

示例：

::*> volume move modify -vserver cluster4_svm1 -volume testmove -cutover-action wait

::*> volume move show

Vserver Volume State Move Phase Percent-Complete Time-To-Complete

--------- ---------- -------- ---------- ---------------- ----------------

cluster4_svm1

testmove alert cutover_hard_deferred

98%

回答1. 是的，数据正在持续传输，可通过命令'vol move show -ins' 观察到这一点：

示例：
ontap913：：> vol move show -ins

Vserver Name: test1 Volume Name: voltest2 Actual Completion Time: - Bytes Remaining: 136.0KB Destination Aggregate: aggr2_node1 Detailed Status: Cutover Deferred, Waiting for user intervention (2.52MB Sent)::Volume move job preparing transfer. Estimated Time of Completion: - Managing Node: ontap913-01 Percentage Complete: 94% Move Phase: cutover_hard_deferred Estimated Remaining Duration: - Replication Throughput: 196KB/s Duration of Move: 00:20:43 Source Aggregate: aggr1_node1 Start Time of Move: Fri Nov 01 13:19:17 2024 Move State: alert Is Source Volume Encrypted: false Encryption Key ID of Source Volume: Is Destination Volume Encrypted: false Encryption Key ID of Destination Volume:

ontap913::> vol move show -ins

Vserver Name: test1 Volume Name: voltest2 Actual Completion Time: - Bytes Remaining: 124.0KB Destination Aggregate: aggr2_node1 Detailed Status: Cutover Deferred, Waiting for user intervention (2.71MB Sent)::Volume move job preparing transfer. Estimated Time of Completion: - Managing Node: ontap913-01 Percentage Complete: 94% Move Phase: cutover_hard_deferred Estimated Remaining Duration: - Replication Throughput: 188KB/s Duration of Move: 00:21:40 Source Aggregate: aggr1_node1 Start Time of Move: Fri Nov 01 13:19:17 2024 Move State: alert Is Source Volume Encrypted: false Encryption Key ID of Source Volume: Is Destination Volume Encrypted: false

问题2：由于上述状态、将触发转换、但未按以下方式完成消息、然后暂停卷移动、源卷上的新数据是否会继续复制到目标卷？

示例：

::*> vol move trigger-cutover -vserver cluster4_svm1 -volume testmove -force true

Detailed Status: Waiting to Cutover. (Preparing source volume for cutover: Deduplication is not ready for volmove cutover Sent)::Reason: xx.xxTB Volume move job monitoring transfer of data.

::*> vol move pause -vserver cluster4_svm1 -volume testmove

答2.否、新数据将暂停传输到目标卷。

第3季度。复制吞吐量约为5 MB/秒是否正常？

回答3.复制吞吐量取决于系统情况、例如工作负载、同时执行了多少卷移动、客户端IO、效率等。有关详细信息、请参见文档： Is Storage Performance Impered your volume mover or cutover？

问题4：如何将上述卷移动恢复为转换等待状态。

答4.由于tigger-cutover 已通过-force true 选项实施、然后它在此状态下暂停、因此可通过'vol move show -ins' 命令检查以下内容、使其无法将卷移动恢复到转换状态、因此转换将强制执行。

Specified Action For Cutover: force

如果需要使用转换来等待此卷移动、请恢复并立即中止此操作、并计划一次新的卷移动、因为已清除现有移动。

示例：

::*> vol move resume -vserver cluster4_svm1  -volume testmove 
 ::*> vol move abort -vserver cluster4_svm1  -volume testmove

适用场景

问题解答

追加信息