Perhaps you are looking at rotating out stale files in the remote or backup_upload_connection
folder. Gitlab is not able to remove stale backups from this or any other remote locations. The backup_keep_time
is only for its internal backup_path
which is defaulted to /var/opt/gitlab/backups
.
I am planning to run a cron job separately which deletes all but 10 of the newest files in my remote, NFS mounted, backup folder.
ls -dt */ | tail -n +11 | xargs rm -rf
See this merge request:
https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1453
And this diff:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5567/diffs
Note that the `backup_keep_time` configuration option only manages local
files. GitLab does not automatically prune old files stored in a third-party
object storage (e.g. AWS S3) because the user may not have permission to list
and delete files. We recommend that you configure the appropriate retention
policy for your object storage. For example, you can configure [the S3 backup
policy here as described here](http://stackoverflow.com/questions/37553070/gitlab-omnibus-delete-backup-from-amazon-s3).