Skip to main content
NetApp Knowledge Base

What is the behavior of snapshots that are created when doing volume clones?

  1. Last updated
  2. Save as PDF
Views:
142
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • FlexClone volumes

Answer

  • Creating a volume clone with volume clone create automatically creates a snapshot on the parent volume if no base snapshot is specified.

::> volume clone create -vserver test222 -flexclone test1_clone -type RW -parent-volume test1
[Job 8414] Job succeeded: Successful

::>  snapshot show -vserver test222 -volume test1
                                                                 ---Blocks---
Vserver  Volume   Snapshot                                  Size Total% Used%
-------- -------- ------------------------------------- -------- ------ -----
test222  test1
                  clone_test1_clone.2025-09-03_150645.0    124KB     1%   40%

Note:

  • When a volume is cloned, a snapshot of the parent volume is taken to capture its state.
  • This snapshot remains "Busy" and is retained until the clone is fully deleted.

::> snapshot show  -vserver test222 -volume test1 -snapshot clone_test1_clone1.2025-09-03_151505.0

                                    Vserver: test222
                                     Volume: test1
                                   Snapshot: clone_test1_clone.2025-09-03_150645.0
                              Snapshot Busy: true
                             List of Owners: volume clone

 

  • Delete the above snapshot need to purge the created clone volume as well
    • Procedure to delete the snapshot created for the clone:
  1. Set advanced privilege.

cluster::> set advanced

  1. Take the cloned volume offline.

cluster::*> volume offline -vserver <svm_name> -volume <clone_vol>

  1. Delete the cloned volume.

cluster::*> volume delete -vserver <svm_name> -volume <clone_vol>

  1. Purge the deleted clone volume from the recovery queue.

cluster::*> volume recovery-queue show -vserver <svm_name>
cluster::*> volume recovery-queue purge -vserver <svm_name> -volume <clone_vol>

Refer:

  1. Confirm the Snapshot is no longer busy.

cluster::*> snapshot show -vserver <svm_name> -volume <parent_vol> -snapshot <base_snap>

Expected after purge:
busy: false
owners: -

  1. Delete the base Snapshot.

cluster::*> snapshot delete -vserver <svm_name> -volume <parent_vol> -snapshot <base_snap>

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.