Skip to main content
NetApp Knowledge Base

Snapshot Deletion Issues in Trident with ONTAP and CloneSplit Behavior

  1. Last updated
  2. Save as PDF
Views:
3
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • Trident
  • Velero or any 3rd party backup solution

Issue

  • Snapshots created for Kubernetes Persistent Volumes (PVs) via Trident were not being deleted as expected after backup operations.
  • Velero logs showed snapshot deletion requests, but Trident returned errors such as:

level=error msg="Unable to delete snapshot from backend." error="snapshot ... is busy"
level=error msg="GRPC error: rpc error: code=Unknown desc=snapshot ... is busy"
level=info msg="Began splitting clone from snapshot."

  • There are offline clones and their related snapshots remaining on the storage after the Velero backup.

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.