You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have installed Velero that uses Kopia as snaphot uploader to Minio object storage.
There is a scheduled backup job which creates regular backups. When some of the backups TTL expires, backup is regularly deleted but space in the object storage is not reclaimed.
I guess there is a problem with maintenance jobs that should be executed automatically in the background. Quick cycle Interval is customised (for the test) to 2mins. When the timer goes off, there is only displayed next run: now and nothing is happening.
When I execute maintenance manually, everything works as expected. Timer is reseted to 2mins and when goes off there is again next run: now. Same situation is with the Full cycle job.
At the Recent Maintenance Runs there is only one record (when repository is initialised).
Owner: default@default
Quick Cycle:
scheduled: true
interval: 2m0s
next run: now
Full Cycle:
scheduled: true
interval: 24h0m0s
next run: 2024-04-26 17:58:39 CEST (in 8h22m58s)
Log Retention:
max count: 10000
max age of logs: 720h0m0s
max total size: 1.1 GB
Object Lock Extension: disabled
Recent Maintenance Runs:
cleanup-epoch-manager:
2024-04-25 17:58:40 CEST (0s) SUCCESS
cleanup-logs:
2024-04-25 17:58:40 CEST (0s) SUCCESS
full-rewrite-contents:
2024-04-25 17:58:40 CEST (0s) SUCCESS
snapshot-gc:
2024-04-25 17:58:39 CEST (0s) SUCCESS
The text was updated successfully, but these errors were encountered:
I have installed Velero that uses Kopia as snaphot uploader to Minio object storage.
There is a scheduled backup job which creates regular backups. When some of the backups TTL expires, backup is regularly deleted but space in the object storage is not reclaimed.
I guess there is a problem with maintenance jobs that should be executed automatically in the background. Quick cycle Interval is customised (for the test) to 2mins. When the timer goes off, there is only displayed next run: now and nothing is happening.
When I execute maintenance manually, everything works as expected. Timer is reseted to 2mins and when goes off there is again next run: now. Same situation is with the Full cycle job.
At the Recent Maintenance Runs there is only one record (when repository is initialised).
The text was updated successfully, but these errors were encountered: