FlexClone volumes can be managed similarly to regular FlexVol volumes, with a few important differences.
For instance, the changes made to the parent FlexVol volume after the FlexClone volume is created are not reflected in the FlexClone volume.
The following list outlines important facts about FlexClone volumes:
- A FlexClone volume is a point-in-time, writable copy of the parent FlexVol volume.
- You must install the license for the FlexClone feature before you can create FlexClone volumes.
- A FlexClone volume is a fully functional FlexVol volume similar to its parent.
- A FlexClone volume is always created in the same aggregate as its parent.
- A traditional volume cannot be used as the parent of a FlexClone volume.
To create a copy of a traditional volume, you must use the
vol copy command, which creates a distinct copy that uses additional storage space equivalent to the amount of storage space used by the volume you copied.
- Because a FlexClone volume and its parent share the same disk space for common data, creating a FlexClone volume is instantaneous and requires no additional disk space (until changes are made to the FlexClone volume or its parent).
- A FlexClone volume is created with the same volume guarantee as its parent.
The volume guarantee setting is enforced for the new FlexClone volume only if there is enough space in the containing aggregate.
- A FlexClone volume is created with the same space reservation and fractional reserve settings as its parent.
- A FlexClone volume is created with the same Snapshot schedule as its parent.
- A FlexClone volume is created with the same language setting as its parent.
- The common Snapshot copy shared between a FlexClone volume and its parent volume cannot be deleted while the FlexClone volume exists.
- While a FlexClone volume exists, some operations on its parent are not allowed, such as deleting the parent volume.
- You can sever the connection between the parent volume and the FlexClone volume.
This is called
splitting the FlexClone volume. Splitting removes all restrictions on the parent volume and causes the FlexClone volume to use its own additional disk space rather than sharing space with its parent.
Attention: Splitting a FlexClone volume from its parent volume deletes all existing Snapshot copies of the FlexClone volume, and disables the creation of new Snapshot copies while the splitting operation is in progress.
If you want to retain the Snapshot copies of the FlexClone volume, you can move the FlexClone volume to a different aggregate by using the vol move command. During the volume move operation, you can also create new Snapshot copies, if required. For more information about the volume move operation, see the Data ONTAP SAN Administration Guide for 7-Mode.
- Quotas applied to the parent volume are
not automatically applied to the FlexClone volume.
- The clone of a SnapLock volume is also a SnapLock volume, and inherits the expiry date of the parent volume. This date cannot be changed, and the volume cannot be destroyed before the expiry date. For more information about SnapLock volumes, see the Data ONTAP Archive and Compliance Management Guide for 7-Mode.
- When a FlexClone volume is created, any LUNs present in the parent volume are present in the FlexClone volume but are unmapped and offline.
