Convert ONTAP FlexVol volumes to FlexGroup volumes
Beginning with ONTAP 9.7, you can perform an in-place conversion of a FlexVol volume to a FlexGroup volume without requiring a data copy or additional disk space. You can convert a FlexVol volume when you want to expand it beyond its space limit. Converting a FlexVol volume to a FlexGroup volume provides higher performance as well as automatic load distribution and scalability.
-
Converting FlexVol volumes to FlexGroup volumes is a non-disruptive operation. Conversion normally takes a few seconds, without taking the volume offline or remounting shares and exports, so clients can continue accessing data.
-
The operations and configurations on the FlexVol volume must be compatible with the conversion process.
-
Beginning with ONTAP 9.20.1, ONTAP provides recommendations to convert FlexVol volumes to FlexGroup volumes through EMS notifications and prompts at the CLI when you modify FlexVol volume capacity. When you perform a conversion, you can expand the FlexGroup volume at the time of conversion instead of having to create a FlexGroup volume with the same capacity as the original FlexVol volume.
-
The FlexVol volume that is being converted must be online.
-
The operations and configurations on the FlexVol volume must be compatible with the conversion process.
Check for the following conditions that can prevent the conversion from succeeding:
-
Anything on the volume that is not yet supported with FlexGroup volume has been disabled or removed; for example, SAN LUNs, Windows NFS, SMB1, snapshot naming/autodelete, vmalign set, SnapLock with releases earlier than ONTAP 9.11.1 (SnapLock is supported beginning with ONTAP 9.11.1), space SLO, or logical space enforcement/reporting. For more information see Supported and unsupported configurations for FlexGroup volumes.
-
With releases earlier than ONTAP 9.10.1, SVM-DR is disabled on the owning SVM of the FlexVol volume. Beginning with ONTAP 9.10.1, you can convert a FlexVol volume to a FlexGroup volume on an SVM-DR source.
-
The FlexVol volume must not be the parent of NetApp FlexClone volumes. The volume being converted cannot be a parent or a clone.
-
The volume cannot be a NetApp FlexCache origin volume.
-
For ONTAP 9.7 and earlier, NetApp snapshots must not exceed 255. For ONTAP 9.8 and later, 1023 snapshots are supported.
-
The volume must not be associated with an application. This is applicable to ONTAP 9.7 only. The limitation is removed in ONTAP 9.8.
-
Storage efficiencies have been disabled. These can be reenabled after conversion.
-
The cannot convert if a volume is the source of a SnapMirror relationship, and the destination has not yet been converted.
-
If the volume is part of an active (not quiesced) SnapMirror relationship, the relationship must be quiesced.
-
Autonomous Ransomware Protection has been disabled on the volume. You should not enable it again until the conversion is complete.
-
Quotas have been disabled. They can be reenabled after conversion.
-
Volume names are 197 characters or less.
-
ONTAP processes must not be running, such as mirroring, jobs, wafliron, NDMP backup, and inode conversion in process.
-
The volume must not be an SVM root volume.
-
The volume must not be too full.
If any of these incompatibilities exist, an error message is generated if the FlexVol volume, and the volume conversion is aborted. You can take corrective actions and retry the conversion.
-
-
If a FlexVol volume is currently at 80% or greater maximum capacity, consider copying the data to a newly created FlexGroup volume instead of performing an in-place conversion. Although FlexGroup member volumes will naturally rebalance over time, converting a high-capacity FlexVol volume to a FlexGroup volume may create performance or balance issues that will not quickly be rebalanced across member volumes.
Converting a very large FlexGroup volume results in a very full FlexGroup volume member constituent, which can create performance issues. For more information, see the section called "When not to create a FlexGroup volume" in the TR FlexGroup volumes - Best Practices and Implementation Guide.
-
Verify that the FlexVol volume is online:
volume show -fields vol_name volume-style-extended,statecluster-1::> volume show my_volume -fields volume-style-extended,state vserver volume state volume-style-extended ------- --------- ------ --------------------- vs0 my_volume online flexvol
-
Verify whether the FlexVol volume can be converted without issues:
-
Log in to the advance privilege mode:
set -privilege advanced -
Verify the conversion process:
volume conversion start -vserver vs1 -volume flexvol -check-only trueYou must rectify all errors before converting the volume.
You cannot convert a FlexGroup volume back to a FlexVol volume.
-
-
Start the conversion:
volume conversion start -vserver svm_name -volume vol_namecluster-1::*> volume conversion start -vserver vs0 -volume my_volume Warning: Converting flexible volume "my_volume" in Vserver "vs0" to a FlexGroup will cause the state of all Snapshot copies from the volume to be set to "pre-conversion". Pre-conversion Snapshot copies cannot be restored. Do you want to continue? {y|n}: y [Job 57] Job succeeded: success -
Verify that the conversion is successful:
volume show vol_name -fields volume-style-extended,statecluster-1::*> volume show my_volume -fields volume-style-extended,state vserver volume state volume-style-extended ------- --------- ------ --------------------- vs0 my_volume online flexgroup
The FlexVol volume is converted to a single-member FlexGroup volume.
You can expand the FlexGroup volume, as required.