How FlexClone volumes work

FlexClone volumes can be managed similarly to regular FlexVol volumes, with a few key differences.

The following list outlines some key facts about FlexClone volumes:

•	A FlexClone volume is a point-in-time, writable copy of the parent volume. Changes made to the parent volume after the FlexClone volume is created are not reflected in the FlexClone volume.

•	FlexClone volumes are fully functional volumes; you manage them just as you do the parent volume.

•	A FlexClone volume is always created in the same aggregate as its parent.

•	A FlexClone volume is always created in the same Vserver as its parent.

•	A FlexClone volume can itself be cloned to create another FlexClone volume.

•	A FlexClone volume and its parent share the same disk space for any common data.

This means that 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.

•	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 to use its own additional disk space rather than sharing space with its parent.

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.

•	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 7-ModeArchive and Compliance Management Guide

•	When a FlexClone volume is created, any LUNs present in the parent volume are present in the FlexClone volume but are unmapped and offline.

Note: For more detailed information about FlexClone volumes, refer to the Data ONTAP 7-ModeStorage Management Guide.