Skip to main content
NetApp Knowledge Base

What's the volume move specific action when using option wait to cutover?

  1. Last updated
  2. Save as PDF
Views:
732
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

ONTAP 9

Answer

Q1.  Implement a volume move operation as below by using the option wait to cutover and when it is completed to  cutover_hard_deferred stage, will the new data on the source volume continue to be copied to the dest volume?
 
Example:
::*> 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%
 
A1.  Yes, the data is being transferred continually which can be  observed from the command 'vol move show -ins' :
 
Example:
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
 

 
 
Q2. As the above status, triggers cutover but it is not completed as below message, then paused the volume move, will the new data on the source volume continue to be copied to the dest volume?
 
Example:
::*> 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 
 
A2. No, the new data is paused to transfer to dest volume.
 
 
Q3. Is that normal for the Replication Throughput around 5MB/sec ?
 
A3. The Replication Throughput depends on the system situation, such as workload, how many volume moves have been implemented at the same time, client IO, efficiency etc, refer to the doc for details:  Is Storage Performance Impacting your volume Move or Cutover? 
 
 
Q4. How to resume the above volume move to cutover wait status.
 
A4. Since the tigger-cutover has been implemented by -force true option, and then it paused in such status, from the 'vol move show -ins'  command can check below, so  it can't resume volume move to cutover status,  the cutover will be executed as force. 
 
Specified Action For Cutover: force
 
If it needs to use cutover wait for this volume move, resume and then abort it immediately and schedule a new volume move since the existing move is clear.
 
Example:
::*> vol move resume -vserver cluster4_svm1  -volume testmove 
::*> vol move abort -vserver cluster4_svm1  -volume testmove 
 

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.