You can nondisruptively move a volume from one aggregate to another within a storage system. You can continue to access data in the LUNs during the volume move.
Before you begin
Before the volume move enters the cutover phase, you must ensure that any existing synchronous SnapMirror relationships established on the source volume are destroyed. You can resynchronize the SnapMirror relationships after the volume move is completed.
About this task
- A temporary volume is created at the beginning of the volume move.
You should not change the contents, state, or attributes of the destination volume, or create any replication, disaster recovery, SnapVault, or qtree SnapMirror relationship with other volumes for the duration of the move.
- MetroCluster relationships are not affected by the volume move.
If your volume guarantee is set to none, the fractional reserve of the volume is automatically set to 0 after the move is completed.
Step
- Start the volume move by entering the following command:vol move start srcvol dstaggr [-k] [-m | -r num_cutover_attempts] [-w cutover_window] [-o] [-d]
srcvol specifies the source volume.
dstaggr specifies the destination aggregate.
-k retains the source volume after a successful move. The source volume remains offline.
-m specifies that the volume move does not initiate automatic cutover. The system continuously runs updates and you can initiate manual cutover at any point during the volume move.
num_cutover_attempts specifies the number of cutover attempts. The minimum number of cutover attempts is one and the default number of attempts is three. If cutover cannot be completed in the specified number of attempts, then the volume move is paused.
cutover_window specifies the duration of the cutover window. The default and minimum value is 60 seconds.
-o displays warning messages on the console and the operation continues.
-d runs all the data copy phase checks. If any of the checks fail, error messages are displayed on the console and the operation is terminated.
Result
If the volume move is successful, the destination volume retains the following:
- Snapshot copies of the source volume
- Attributes of the LUNs from the source volume in the corresponding LUNs in the destination volume