Hi all,
I'm using Kasten K10 with a StorageClass set to Retain and Longhorn as the CSI driver. After snapshots are created by K10, they’re left in a detached state — which I understand is expected due to the Retain policy.
However, is there a setting in the Helm chart (or elsewhere) that allows K10 to clean up these volumes/snapshots automatically after a backup is deleted?
PS: A similar post have been created 3 years ago, but i were hoping that a fix had been provided.
From the screenshot, It appears that resource accumulation is occurring in the kasten-io namespace. The default behavior is a PersistentVolume (PV) is being created from a Kasten copy of the VolumeSnapshotClass associated with the protected application and mounted to a copy-vol-data pod for export. With the VolumeSnapshotClass set to deletionPolicy: Retain, snapshots are expected to persist until after the export is successful. However, the Kasten Lifecycle Manager should clean up temporary resources, such as the PV and pod.
The persistence of these resources suggests a potential issue with either the Lifecycle Manager or the export process. Need to review the logs to diagnose and resolve this, please open a support ticket via the Veeam Support Portal. BR.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
