Table of ContentsView in Frames

Moving a volume

You can move a FlexVol volume to a different aggregate, node, or both within the same Storage Virtual Machine (SVM).


  1. If you are moving a data protection mirror and you have not initialized the mirror relationship, initialize the mirror relationship by using the snapmirror initialize command.
    Data protection mirror relationships must be initialized before you can move one of the volumes.
  2. Use the volume move target-aggr show command to determine an aggregate to which you can move the volume.
    This step ensures that you select an aggregate that has enough space for the volume, that is, the available size is bigger than the volume that you are moving.
    cluster1::> volume move target-aggr show -vserver vs2 -volume user_max
    Aggregate Name   Available Size   Storage Type
    --------------   --------------   ------------
    aggr2            467.9GB          FCAL
    node12a_aggr3    10.34GB          FCAL
    node12a_aggr2    10.36GB          FCAL
    node12a_aggr1    10.36GB          FCAL
    node12a_aggr4    10.36GB          FCAL
    5 entries were displayed.
    The resulting list shows that the vs2 volume can be moved to any of the listed aggregates.
  3. Run a validation check on the volume by using the volume move start -perform-validation-only command to ensure that the volume can be moved to the intended aggregate.
  4. Use the volume move start command to move a volume.
    The following command moves a volume named user_max on an SVM named vs2 to an aggregate named node12a_aggr3. The administrator previously determined that clients accessing the data in the volume can tolerate an I/O timeout of, at most, 120 seconds. The move runs as a background process.
    cluster1::> volume move start -vserver vs2 -volume user_max
    -destination-aggregate node12a_aggr3 -cutover-window 120
  5. Use the volume move show command to determine the command’s status.
    The following example shows the state of a volume move that completed the replication phase and is in the cutover phase.
    cluster1::> volume move show                                                           
    Vserver   Volume     State    Move Phase  Percent-Complete Time-To-Complete 
    --------- ---------- -------- ----------  ---------------- ---------------- 
    vs2       user_max   healthy  cutover     -                -                
  6. If the volume move operation does not complete the final phase after three attempts and goes into a cutover deferred state, use the volume move trigger-cutover command to attempt to complete the move.
    The following command forces the volume move operation to finish.
    cluster1::> volume move trigger-cutover -vserver vs2 
    -volume user_max -force true
    Note: Forcing the volume move operation to finish can disrupt client access to the volume you are moving.