... | ... | @@ -962,20 +962,21 @@ More work is underway to improve monitoring in [issue 33921](https://gitlab.torp |
|
|
|
|
|
## Backups
|
|
|
|
|
|
There is a cronjob configured via the gitlab puppet monitor that runs
|
|
|
every night at 2:00AM UTC. This will basically run `$ gitlab-backup `
|
|
|
and will create a tarball under `/srv/gitlab-backup/`.
|
|
|
|
|
|
There is also a config backup job (in
|
|
|
`/etc/cron.d/gitlab-config-backup`) that makes sure to backup the
|
|
|
content of `/var/opt/gitlab/gitlab-rails/etc/` is backed up, because
|
|
|
that is not covered by the `gitlab-backup` command.
|
|
|
|
|
|
Another cron job purges backups older than two days, in
|
|
|
`/etc/cron.d/gitlab-rotate-backup`, so that we don't keep too many
|
|
|
copies on the server. It is assumed that the existing [howto/backup](howto/backup)
|
|
|
system will pick up those copies and store them for our normal
|
|
|
rotation periods.
|
|
|
There is a backup job (in the `git` user crontab) that makes sure to
|
|
|
backup the content of `/var/opt/gitlab/gitlab-rails/etc/` are backed
|
|
|
up. We use this instead of the backup system provided by the GitLab
|
|
|
Puppet module, because that is not covered by the `gitlab-backup`
|
|
|
command. This is implemented with the `tpo-gitlab-backup`, a simple
|
|
|
wrapper script which calls `gitlab-backup` and performs the
|
|
|
configuration backup and rotation.
|
|
|
|
|
|
It is assumed that the existing [howto/backup](howto/backup) system
|
|
|
will pick up those copies and store them for our normal rotation
|
|
|
periods.
|
|
|
|
|
|
Ideally, this rather exotic backup system would be harmonized with our
|
|
|
existing backup system, but this would require (for example) using our
|
|
|
existing PostgreSQL infrastructure ([issue 20](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/20)).
|
|
|
|
|
|
## Other documentation
|
|
|
|
... | ... | |