Skip to main content
NetApp Stage KB

Trident is Unable to delete snapshot from backend, causing PVC to hang in terminating

Last Updated:

Applies to

  • Trident for Kubernetes/Openshift up to 21.07.1
  • Astra Trident for Kubernetes/Openshift 21.10.0 and higher
  • CommVault for Kubernetes
  • VSERVER-DR or MCC (Metrocluster)


The following errors occur while Trident is attempting to delete the snapshots on the PV volume, so the volume can be deleted:
time="<DATETIME>" level=info msg="Determined topology labels for node: map[]" node=<K8S_NODE_N> requestID=<UUID> requestSource=REST
time="<DATETIME>" level=error msg="Could not begin splitting clone from snapshot."
    error="error splitting clone: API status: failed,
    Reason: This volume cannot be split as it is configured for protection using Vserver level snapmirror.
        Change the protection type using \"volume modify\" command to make it unprotected., Code: 13001"
    parentVolumeName=<VOLUME_PVC_NAME> requestID=<UUID>
    requestSource=CSI   snapshotName=snapshot-<UUID>
time="<DATETIME>" level=error msg="Unable to delete snapshot from backend." backend=<BACKEND_NAME>
    error="snapshot snapshot-<UUID> backing volume <VOLUME_PVC_NAME> is busy" requestID=<UUID>
    requestSource=CSI snapshot=snapshot-<UUID>   volume=<PVC-NAME>

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.