Skip to main content
NetApp Knowledge Base

CONTAP-719981: SnapDB population should not continuously restart on bursts of snapshot deletes

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

Issue

  • Under heavy snapshot-delete activity (bursts of concurrent snapshot deletions), SnapDB (SDB) population for a volume can be repeatedly restarted and never complete.
  • This can leave the volume’s SnapDB in a NOTREADY state for an extended period and fail Snapshot Coordination or Snapmirror or SVM DR updates

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.