What considerations should be made before moving a volume?
Applies to
Answer
If you are upgrading the release family for a cluster, do not move a volume until after you upgrade all of the nodes in the cluster.
This recommendation prevents you from inadvertently attempting to move a volume from a newer release family to an older release family.
The source volume must be consistent.
If you have assigned one or more aggregates to the associated storage virtual machine (SVM), the destination aggregate must be one of the assigned aggregates.
You cannot move a volume to or from a taken-over CFO aggregate.
If a volume that contains LUNs is not NVFAIL enabled before you move it, the volume will be NVFAIL enabled after you move it.
You can move a volume from a Flash Pool aggregate to another Flash Pool aggregate.
The caching policies of that volume are also moved.
The move might affect volume performance.
You can move volumes between a Flash Pool aggregate and a non-Flash Pool aggregate.
If you move a volume from a Flash Pool aggregate to a non-Flash Pool aggregate, ONTAP displays a message warning you that the move might affect volume performance and asks whether you want to continue.
If you move a volume from a non-Flash Pool aggregate to a Flash Pool aggregate, ONTAP assigns the
autocaching policy.
Volumes have the data-at-rest protections of the aggregate they reside on. If you move a volume from an aggregate that consists of NSE drives to one that does not, the volume no longer has NSE data-at-rest protection.
