Skip to main content
NetApp Knowledge Base

Snap Creator 3.4.1 fails to delete snapshots on the first storage defined in VOLUMES

Views:
126
Visibility:
Public
Votes:
0
Category:
snap-creator-framework
Specialty:
snapx
Last Updated:

Applies to

Snap Creator Framework (SCF) 4.3.1

Issue

When defining more than one SVM or Filer in the VOLUMES entry with each their own volumes, during the retention snapshot cleanup, it attempts to delete the snapshots on the volumes defined for the second (or later) storage, not finding the snapshot to delete:
 
DEBUG: STORAGE-02015: Removing Snapshot copy [<CONFIG>_<DATETIME>] on [<VOLUME1>] failed with error [netapp.manage.NaAPIFailedException: Volume "<VOLUME1>" does not exist in Vserver "<STORAGE2>". Reason: entry doesn't exist.  (errno=13040)]
INFO: SCF-00212: Snapshot copy [<CONFIG>_<DATETIME>] cannot be deleted for [<STORAGE2>]:[<VOLUME1>]. Retry attempt [1] after [5] seconds.
Snapshots on the first listed SVM/Filer with volumes will therefore remain behind unintentionally.

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.