Release notes
How Snapshot copies work with FlexClone files and FlexClone LUNs
Suggest changes
-
PDF of this doc site
-
Cluster administration
-
Volume administration
-
Logical storage management with the CLI
-
-
NAS storage management
-
Configure NFS with the CLI
-
Manage NFS with the CLI
-
Manage SMB with the CLI
-
Manage file access using SMB
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-
Collection of separate PDF docs
Creating your file...
There is a synergy between Snapshot copies and the FlexClone files and FlexClone LUNs. If you work with these technologies, you should be aware of what is possible as well as the relevant restrictions.
You can create a FlexClone file or FlexClone LUN from an existing Snapshot copy. The copy is based on the the parent files and parent LUNs contained in a FlexVol volume.
You cannot manually delete a Snapshot copy from which FlexClone files or FlexClone LUNs are currently being created. The Snapshot copy remains locked until the background block-sharing process is completed. If you try to delete a locked Snapshot copy, the system displays a message asking you to retry the operation after some amount of time. In this case, you need to continue retrying the deletion operation. You'll be able to delete the Snapshot copy after the block sharing is done.