Retention Issues with Kasten K10 on Synology NFS – Old Backups Not Deleted

​@Madi.Cristil ​@safiya please move this one too in to the Kasten / Kubernetes section for help.

Good morning,

are there any updates regarding the issue we discussed?
 

From what I understand, Kasten handles cleanup actions and restore point deletions through its interface. However, when I log into my Synology and inspect the backup folder, I still see that no data has actually been removed.
 

Could you please look into this? If the repository continues to accumulate data without proper cleanup, it could eventually reach full capacity and cause further problems.
 

Thank you in advance!
 

Best regards.

Good morning,
I'm facing a retention issue with backups stored in an S3 location, and it's strikingly similar to a problem I previously encountered using NFS (link to previous post).
Here’s the current setup:

Retention policy: 7 days + 1 weekly backup
Hardening: 7 days
Backup size: ~80GB (PV containing a DB)

Despite this configuration, no data has been deleted from the S3 bucket after more than a month. I’ve been monitoring the actual data written/deleted in the bucket, and it remains unchanged. However, the Kasten storage report shows a graph indicating proper data deletion, which doesn’t reflect the reality.

This is a similar behavior I saw with NFS previously — retention policies appear to be applied in the UI, but the underlying data is not being cleaned up.

Has anyone else experienced this with S3 or other storage backends?
Could this be related to how Kasten handles object lifecycle, metadata, or versioning in S3?
Any help or insights would be greatly appreciated!

Thanks,
Best Regards

​@Hagag Can you assist here when you have a moment? thanks!

Hi ​@rockandstone - did you get an answer to your question as yet?  If so please mark the best answer so it helps the community with similar questions.

Good morning ​@Chris.Childerhose,

I haven’t received an answer yet, so I wanted to share an update. I had to switch to an S3 bucket, but I’m still seeing that the backup size is significantly larger than what Kasten reports in the dashboard. Additionally, the Storage Usage page shows a total external storage usage that includes data from the old NFS configuration—even though I removed it from Kasten and manually deleted it from the NAS (it wasn’t cleaned up automatically after weeks).

Another point: in the S3 bucket, data started to delete only after more than 4 weeks, even though the policy was set to 7 days of immutability and 7 days of retention. This makes it difficult to predict storage consumption and retention behavior.

At this stage, I’m unsure how to troubleshoot or fully understand the mechanics behind backup size, retention, and GFS policies. There seem to be too many unpredictable behaviors. This is surprising because I’ve really appreciated the product so far, but right now I can’t rely on NFS or accurately estimate cloud utilization in this way.

Any guidance or best practices would be greatly appreciated.

Thank you very much,
Best regards.