Skip to main content
NetApp Knowledge Base

Snapshot retention stops working after SnapCenter or SMCore restart

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

Applies to

  • SnapCenter Server (SC) 4.8 / 4.9
  • SnapCenter Plug-in for Microsoft SQL Server (SCSQL) 4.8 / 4.9

Issue

  • Backup retention stops working after SC server is rebooted, or SMCore service on SC server is restarted.
  • Re-entering the SVM credentials for the storage connections after a reboot / restart results in retention working again.
  • SnapManagerWeb log reports that the snapshot has been deleted as per the retention policy, however the snapshot still remains in ONTAP.
  • The following entry is seen in the SCW_<Job_Id>.log:

Verbose SDW PID=[<PID>] TID=[<TID>] The storage is not in the storage systemId cache: Available cached storage are...

 

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.