Skip to main content
NetApp Knowledge Base

TridentProtect Backups Stuck in Running State After Upgrade to 25.10

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

Applies to

  • Trident 25.10
  • Trident Protect 25.10
  • OpenShift Virtualization
  • Kubevirt
  • S3 backups via Trident Protect

Issue

  • After upgrading Trident and Trident Protect to version 25.10.0, backup jobs for applications remain stuck in a Running state indefinitely
  • Most Persistent Volume Claims (PVCs) successfully copy data to S3, but 1–3 jobs per backup show volumeBackupCompleted:false and are hung on the volumeSnapshotCopyDeleted task.
  • This can be seen intermittently and can affect different PVCs on each operation

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.