-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
velero backup delete is not deleting kopia data from s3 #8599
Comments
@kaovilai I'm not expecting this to be immediate, but even after 2 days i see kopia data in my S3 repo. |
Once kopia data is created, some folder will remain even if all backups are deleted. Look at the remaining size if it was reduced. |
My team has tests and validated that size do reduce. So that is sufficient IMO. Concerns are if you have 1TB volume backup and when you delete its still taking up say 200MB. |
Thank you for clarification. I'm also seeing that data chunks are being deleted (when did a test on bigger volumes). Although still that is a bit of mess when kopia is leaving all other files which are not referenced by anything in S3 repo. Expected would be that kopia cleaned this up. |
velero do not delete kopia repos.. it init repos, add snapshots to it, delete snapshots as backups are deleted, but repos stay. |
What steps did you take and what happened:
I created empty s3 repo and did a single backup, and then removing it.
I am expecting the all data that is not referenced by any other backup is deleted.
But on s3 i see the deleted was only content from /backup/testbackup/
but content in /kopia/ is not deleted.
What did you expect to happen:
all backup files and data volume chunks not referenced by any other backup to be deleted
Anything else you would like to add:
Environment:
velero version
): 1.13.2velero client config get features
): velero-plugin-for-csi:v0.7.1 ; velero-plugin-for-aws:v1.9.2kubectl version
): v1.25.16/etc/os-release
): -Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: