Skip to main content
NetApp Knowledge Base

Snapshots are deleted immediately after SnapCenter backup is run

  1. Last updated
  2. Save as PDF
Views:
551
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
SNAPX
Last Updated:

 Applies to

  • SnapCenter Server (SC)
  • SnapCenter Plug-in for Exchange (SCE)
  • SnapCenter Plug-in for VMware vSphere (SCV)

Issue

  • Snapshots are automatically deleted by Data ONTAP immediately after a backup creates it
  • Error seen in the <installation_path>\Program Files\NetApp\SnapCenter\SMCore\log\SMCore_<id>.log:

ERROR SMCore_879223 PID=[3460] TID=[200] ErrorCode (-1), ErrorMessage (Unable to find Snapshot (snapshot_name) on volume (volume_name) from storage (SVM_name_or_IP_address))

  • For SCE, the error may look a little different

Activity 'Renaming VSS Snapshot' failed with error: Rename snapshot '{snapshot_name}' failed:  entry doesn't exist
.Failed in volume 'volume_name',  entry doesn't exist

  • The below error is logged in the EMS-LOG-FILE.GZ log

[ONTAP_NODE]: snap_helper: wafl.volume.snap.autoDelete:info]: Deleting Snapshot copy 'SNAPSHOT_NAME' in volume 'VOLUME_NAME' to recover storage

  • For SCV, the error may look like below

ERROR USDPRDCUSAPSCNTR --- [1738236591-1263] c.n.a.s.c.SnapManagerStorageServiceImpl  : [JobId:223] Mount Backup failed: Failed to create the volume clone.
Failure. job details: [ 1638400 ]: Failed to retrieve snapshot information. Reason: entry doesn't exist. 
, 
ERROR USDPRDCUSAPSCNTR --- [1738236591-1263] c.n.a.m.VmfsMountStrategy                : [JobId:223] Failed to create LUN clone <LUN Name> on volume svm0:<LUN Path> Failed to create the volume clone.
Failure. job details: [ 1638400 ]: Failed to retrieve snapshot information. Reason: entry doesn't exist. 

  • The below error is logged in the audit-m and mgwd log

[kern_audit:info:3589] [traceid:71c8bef2e2629e476d85a5d64fcedf05] 8503e80000014f8a :: cluster:ontapi :: 172.16.2.247:36426 :: svm0:admin :: <netapp version='1.7' xmlns='http://www.netapp.com/filer/admin' vfiler='svm0'><snapshot-multicreate>   <snapshot>snapshot name</snapshot>   <volume-names>     <volume-name>volume name</volume-name>   </volume-names> </snapshot-multicreate></netapp>  :: Pending: 

[kern_mgwd:info:3589] 0x82c913000: 0: INFO: EMS::SNMP: snmpTransmitEvent called for event (name: wafl.volume.snap.autoDelete, seq_num: 144587), trap (type: 1, id: 656, data: Snapshot Autodelete: Deleting snapshot 'snapshot name' in volume 'volume name@vserver:9a0a45c4-fdaa-11ef-8514-d039' to recover storage.)

[kern_audit:info:3589] [traceid:f0e2bd8e60cf9b61a3ddafeb77f47785] 8503e80000014f93 :: cluster:http :: 172.16.2.247:35342 :: USYOTSAN000041:admin :: POST /api/private/cli/volume/clone : {"junction_active":true,"parent_snapshot":"snapshot name","parent_volume":"volume name","flexclone":"clone volume name","use_snaprestore_license":"true","vserver":"svm0","snaplock_type":"non-snaplock"} :: Error: Failed to retrieve snapshot information. Reason: entry doesn't exist

 

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.