You are browsing a read-only backup copy of Wikitech. The primary site can be found at


From Wikitech-static
< GitLab
Revision as of 09:29, 29 October 2021 by imported>Jelto (add information about automated restore)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search is a copy of production GitLab. Currently gitlab2001 is the replica of gitlab1001.

The purpose of the GitLab replica is:

  • to have a almost identical machine with production Gitlab to test changes
  • to verify the installation path developed by S&F for gitlab1001
  • to have a host for failover in case production GitLab breaks (WIP)
  • to have parity with gerrit-replica

The purpose is not to share the load between both GitLab instances.

Manual sync of replica

To manually sync of production GitLab with the replica the latest backups have to be moved from production GitLab to the replica. You can either use the existing rsync configuration or cumin. In most cases the most recent backup should bre present under /etc/gitlab/config_backup/latest and /srv/gitlab-backup/latest and you can skip this step.

Transfer of backup to replica

For rsync, run the following commands on gitlab1001 to sync the latest backup to gitlab2001:

gitlab1001:~# /usr/bin/rsync -avp --delete /etc/gitlab/config_backup/latest/ rsync://
gitlab1001:~# /usr/bin/rsync -avp --delete /srv/gitlab-backup/latest/ rsync://

/config-backup and /data-backup are just module names of the rsyncd config. The backups are copied to /etc/gitlab/config_backup/latest and /srv/gitlab-backup/latest. Or use cumin:

cumin1001:~$ sudo SSH_AUTH_SOCK=/run/keyholder/proxy.sock scp -3
cumin1001:~$ sudo SSH_AUTH_SOCK=/run/keyholder/proxy.sock scp -3

Restore of backup on replica

All restore logic for the replica is handled by a custom shell script which is present on the replica. So the easiest option to restore is to run the script on the replica:


It is also possible to do the restore manually if needed. The GitLab restore guide should be used. The exception here is that we have to keep the gitlab.rb from the replica when restoring the config backup. Before restore, make sure to copy the old gitlab.rb before following the guide.

sudo cp /etc/gitlab/gitlab.rb /etc/gitlab/gitlab.rb.bak

Before restore, make sure the backup can be found by GitLab. So we have to move and rename the backups:

cp /srv/gitlab-backup/latest/latest.tar /srv/gitlab-backup/latest_gitlab_backup.tar

After the restore is finished, the settings have to be reapplied to the replica using gitlab-settings:

./settings --instance --settings-file settings-replica.yaml update

Automated sync of replica

Automated sync and restore between the replica and production GitLab is active. For automated sync of the backups a systemd timer with rsync is configured on production GitLab and rsyncd is running on the replica. The job runs every 24h and transfers the most recent data and config backup to the replica.[1] The actual restore of the backup on the replica is handled by custom shell script and a systemd timer running this script. The restore runs every 24 hours.

The most recent backup can be found in: /etc/gitlab/config_backup/latest and /srv/gitlab-backup/latest.

So make sure to use the timestamp latest when using the gitlab-backup restore BACKUP=latest command and follow the GitLab restore guide.


The usage of gitlab-replica should be mostly internal for testing, troubleshooting and in case of an emergency. Thus login with SSO needs the groups ops, wmf or nda.