Click the exhibit button.
Referring to the exhibit, which statement about the volume move process is true?
A.
Client access to the volume is blocked during this phase of operation.
B.
The initial replication phase sent 39 MB from the source to the destination location.
C.
Client access is being redirected to the destination location during this phase of the operation.
D.
The cutover process failed and is in a holding pattern before being attempted again.
I would choose C.
It is mentioned in ONTAP_90_Volume_Move_Express_Guide, page 8, point 6
0
0
Answer – B
Only 39mb has been replicated on 1 of 3… the destination volume hasn’t completed the baseline transfer.
I would go with Answer C.
0
0
There is no point 6 on page 8!
0
0
Can anybody tell the correct answer? In my mind i would also go with answer C.
0
0
A is correct and here is why:
When a volume move is initiated, a Snapshot copy of the source volume is created and is used as the basis to populate the destination volume. Client systems continue to access the volume from the source destination until all data is moved. At the end of the move process, client access is temporarily blocked. Meanwhile, the system performs a final replication from the source volume to the destination volume, swaps the identities of the source and destination volumes, and changes the destination volume to the source volume. When the move is complete, the system routes client traffic to the new source volume and resumes client access.
And the cutover phase is the last phase in this process. So, client access is temp. blocked.
3
0
Agree, from NetApp documentation https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-vsmg%2Fhome.html
How moving a FlexVol volume works
Knowing how moving a FlexVol volume works helps you to determine whether the volume move satisfies service-level agreements and to understand where a volume move is in the volume move process.
FlexVol volumes are moved from one aggregate or node to another within the same Storage Virtual Machine (SVM). A volume move does not disrupt client access during the move.
Moving a volume occurs in multiple phases:
A new volume is made on the destination aggregate.
The data from the original volume is copied to the new volume.
During this time, the original volume is intact and available for clients to access.
At the end of the move process, client access is temporarily blocked.
During this time the system performs a final replication from the source volume to the destination volume, swaps the identities of the source and destination volumes, and changes the destination volume to the source volume.
After completing the move, the system routes client traffic to the new source volume and resumes client access.
The move is not disruptive to client access because the time in which client access is blocked ends before clients notice a disruption and time out. Client access is blocked for 35 seconds by default. If the volume move operation cannot finish in the time that access is denied, the system aborts this final phase of the volume move operation and allows client access. The system attempts the final phase three times by default. After the third attempt, the system waits an hour before attempting the final phase sequence again. The system runs the final phase of the volume move operation until the volume move is complete.
0
0
+1
0
0
I think A is correct
cutover phase: at the end of the move process there is a cutover phase. During cutover client access is temporarily blocked*. During this short time, a final replication from source volume to the destination volume is being made, identity swap is being made, which changes the destination volume to the source volume. After completion the move, system routes client traffic to the new source volume, resuming client access, and disposing old volume
How come the access is temporarily blocked* during the operation? Didn’t I mention this is a non-disruptive operation? Well – volume move is treated as non disruptive, because the window of blocked access cannot be longer by 45 seconds (by default). In this time window the client will not notice a disruption and will not time-out. If, for some reason ONTAP, will not complete the final phase in planned 45 seconds, system will abort the attempt of the cutover and allow client access to original source volume. Another attempt will be executed later on. You can adjust this 45 seconds window (possible options are from 30 seconds to 300 seconds).
1
0