sameersbn / sameersbn/docker-gitlab
question regarding backup via ZFS snapshot replication and deleting old GitLab backups
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I hope it is okay and helpful also for others
to use GitHub Issues to discuss two GitLab admin questions.
According to the following lines in docker-compose.yml
volumes:
- gitlab-data:/home/git/data:Z
the GitLab data is kept in
/var/lib/docker/volumes/docker-compose_gitlab-data/_data.
All filesystems are on ZFS, and (atomic) snapshots are made and replicated to another machine every day.
Because of this, I disabled the GitLab backup feature in docker-compose.yml
- GITLAB_BACKUP_SCHEDULE=disable
Is this a safe backup strategy for GitLab?
There are still two old backups (tar files) remaining under
/var/lib/docker/volumes/docker-compose_gitlab-data/_data/backups/
taking up quite some space.
Is it safe to manually delete these files?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the backup-related entries in docker-compose.yml and the tar files under /var/lib/docker/volumes/docker-compose_gitlab-data/_data/backups/. Review how ZFS snapshots and replication relate to GitLab's backup feature, then document whether this strategy is safe and whether the old backup files can be deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100