Skip to main content
NetApp Knowledge Base

Snapmirror fails to create a snapshot copy volumes has clones backed by snapshots

Views:
764
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

  • ONTAP
  • SnapMirror
  • SIS File Clone

Issue

  • Snapmirror getting failed with following error:
Failed to create Snapshot copy snapmirror.b99c66c4-42c5-11ea-ac12-d039ea131e6d_2151302974.2024-04-13_224901 on volume svm:prod_volume. (Failed to create Snapshot copy snapmirror.b99c66c4-42c5-11ea-ac12-d039ea131e6d_2151302974.2024-04-13_224901 on volume d5995f9e-601b-11ed-b6e5-13bfcf32b3c8:prod_volume. (File exists))
  • Snapmirror audit logs:
Wed Feb 28 20:13:59 ACDT 2024 FlexGroupScheduledUpdate[Feb 28 19:55:00]:e11123de-0ffb-11ee-85d9-d039ea131e6d Operation-Uuid=d1ae2e4f-d41d-41d3-93f2-a74d25eb209c Group=flexgroup Operation-Cookie=0 action=End source=svm_AWSNAS08:prod_geodata_basins_coop_erom destination=SVM01:prod_volume_dest status=Failure message=Failed to create Snapshot copy snapmirror.b99c66c4-42c5-11ea-ac12-d039ea131e6d_2151302974.2024-02-28_195500 on volume svm:prod_volume.(Failed to create Snapshot copy snapmirror.b99c66c4-42c5-11ea-ac12-d039ea131e6d_2151302974.2024-02-28_195500 on volume d5995f9e-601b-11ed-b6e5-13bfcf32b3c8:prod_volume.(Volume has clones backed by snapshots))
  • On source cluster the creation of snapshot fails with below error.
Wed Feb 28 09:00:03 +0000 [AWSNAS08-01: snapd_cmode: wafl.snap.create.skip.reason:error]: prod_volume_0001  d5995f9e-601b-11ed-b6e5-13bfcf32b3c8: Skipping creation of ADE_1830HRS.2024-02-28_0900 Snapshot copy (Snapshot operation not allowed due to clones backed by snapshots. Try again after sometime.).
  • Manual snapshot creation on source also fails with below error.
cluster::> snapshot create -volume prod_volume -vserver svm -snapshot Manual_Test
Error: command failed: Failed to create snapshot "Manual_Test" of volume "prod_volume" on Vserver
       "svm". Reason: Snapshot operation not allowed due to clones backed by snapshots. Try again after sometime.
  • The volume that was failing to create snapshots has a snapshot owned by SIS Clone
cluster::*>snapshot show -busy true -fields busy,owner,create-time
vserver      volume                         snapshot                    create-time              busy owners
------------ ----------------------------- --------------------------- ------------------------ ---- -----------
svm         prod_volume                     ADE_1830HRS.2024-02-26_0900 Mon Feb 26 09:00:00 2024 true "SIS Clone"
  • The deletion of that snapshot also fails with below error.
AWSNAS08::*> snapshot delete -snapshot ADE_1830HRS.2024-02-26_0900 -vserver svm -volume prod_volume -ignore-owners true
Error: command failed: Snapshot copy "ADE_1830HRS.2024-02-26_0900" of volume "prod_volume " in Vserver
       "svm" has not expired or is locked. Use the "snapshot show -fields owners, expiry-time, snaplock-expiry-time"
       command to view the expiry and lock status of the Snapshot copy.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.