Wasabi - Immutability Period Keeps getting Extended

[sykerzner]

We have Cloud Connect setup with SOBRs. They have a Wasabi Cap tier.

I have found recently, that I can't delete old, long disabled backups. The Immutability period somehow gets set weeks away. This is eve

For instance, I tried to delete a Cloud Backup which had not run since 7/15. When I tried to delete it in July I was told I need to wait until the end of September. When I tried today, I was told I need to wait another 3 weeks.

11/13/2025 2:17:46 PM Error [********************************] Failed to delete backup Error: Unable to delete backup because it is immutable until 05 December 2025 06:08:11.

Has anyone seen this, or know what's causing immutability to be extended?

[edh]

If your target is delete this bucket with backups and your encountering this problem , do it simple.

Delete the access key to the bucket, wait until inmutability disapear in Wasabi system and perform a bucket deletion.

Maybe this is caused by block regeneration done by Veeam but still i didnt encounter this problem.

Regards

[sykerzner]

Oh, thank you edh.
I was wondering in general how to delete the backups in the Wasabi independent of the files in CloudConnect. I am sure Veeam would prefer I don't do any manual deleting, but it comes up...

I actually also opened a ticket and spoke to a tech today. He was telling me that the last Active Chain in a backup will have Immutability pushed forward. In this case, the backup job still existed (but disabled), and the points were non-detached. He's escalating to see what would be the recommended way to clean these up?
Would deleting the job have worked? Would detaching the backup from the Job have worked?
And while I'm at it, did this behavior only change with V12?