Skip to main content
NetApp Knowledge Base

Stale AMU objects and replicatedSnapshots not being garbage‑collected on target clust

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
astra
Last Updated:

Applies to

Trident Protect any version

Issue

  • Inconsistent garbage collection of AppMirrorUpdate (AMU) objects and replicated Snapshots in the AppVault (S3 bucket) on the target cluster within a TridentProtect environment for OpenShift.
  • Some namespaces clean up old AMUs and Snapshots correctly, while others accumulate completed AMUs and Snapshots that are never deleted.

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.