NetApp
Cluster : Storage > Aggregates : Understanding aggregates : How moving a FlexVol volume works

How moving a FlexVol volume works
You can move a FlexVol volume from one aggregate or node to another within the same Vserver for capacity utilization and improved performance, and to satisfy service-level agreements.
Moving a volume does not disrupt client access when the system is moving the volume. Moving a volume occurs in multiple phases:
•
•
During this time, the original volume is intact and available for clients to access.
•
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.
•
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 45 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 runs the final phase of the volume move operation until the volume move is complete or until the default of three attempts is reached. If the volume move operation fails after the third attempt, the process goes into a cutover deferred state and waits for you to initiate the final phase.
You can change the amount of time client access is blocked or the number of times the final phase of the volume move operation, known as cutover attempts, are run if the defaults are not adequate. Also you can determine what the system does if the volume move operation cannot be completed during the time client access is blocked. The volume move start man page contains details about moving a volume without disrupting client access.


Was this topic helpful? Send comments to NetApp.