Velero Backup w/ Kopia not cleaning up old files #8084
Unanswered
ishaanjoshi7-pixel
asked this question in
Community support Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a scenario where my customer has Velero backup configured and a scheduled backup running. FSB Opt-In is enabled, CSI snapshot is disabled, and the default configuration is using Kopia.
Now per customer, after he's moved to kopia, his maintenance tasks aren't completing successfully (I assume maintenance tasks are required to clean up the previous files and dependencies from the repositories before initiating a new backup). Per the command output below, it seems that the maintenance tasks have not completed in a while.
$ velero repo get
NAME STATUS LAST MAINTENANCE
gatekeeper-system-le-k8s-backup-kopia Ready 2024-06-28 16:33:36 +0000 UTC
logging-sidecar-lrfd-le-k8s-backup-kopia Ready 2024-07-08 22:34:04 +0000 UTC
tanzu-system-dashboards-le-k8s-backup-kopia Ready 2024-06-28 16:34:23 +0000 UTC
tanzu-system-ingress-le-k8s-backup-kopia Ready 2024-06-28 16:35:10 +0000 UTC
tanzu-system-monitoring-le-k8s-backup-kopia Ready 2024-06-28 16:35:57 +0000 UTC
I'm seeing errors in the velero pod log indicating "errors pruning repository"
If i check the velero pod logs I see below
time="2024-07-22T21:09:44Z" level=warning msg="error pruning repository" backupRepo=velero/logging-sidecar-lrfd-le-k8s-backup-kopia error="error to prune backup repo: error to maintain repo: error to run maintenance under mode auto: error updating maintenance schedule: unable to complete PutBlob(kopia.maintenance) despite 10 retries: Object already exists." error.file="/go/pkg/mod/github.com/project-velero/kopia@v0.0.0-20231023031817-cf7bbc7f8519/internal/retry/retry.go:94" error.function="github.com/kopia/kopia/internal/retry.internalRetry[...]" logSource="pkg/controller/backup_repository_controller.go:295"
No issues are seen with the with the valero controller pod (except reporting un-successful pruning the logs snippets of which I've shared above) and worker-node pods (which reports everything successful from volume creation to successful backups happening). Please assist me on how should I proceed next.
Beta Was this translation helpful? Give feedback.
All reactions