GitLab System Admin - Hands-On Lab: Omnibus Backup and Restore

This Hands-On Guide demonstrates how to backup and restore your Omnibus GitLab instance

Estimated time to complete: 30 minutes

Objectives

The objective of this lab is to demonstrate how to back up a GitLab instance on a virtual machine, and restore said instance to a previous state. For more information about backing up/restoring a GitLab instance, click here.

Task A. Configure backup settings

Open an SSH session on your GitLab instance server.
Search for the location of backup settings in gitlab.rb.
```
sudo grep -n backup_path /etc/gitlab/gitlab.rb
```
Note the line number for the setting gitlab_rails['backup_path'].
Create a new directory to hold GitLab backups.
```
sudo mkdir /tmp/backups
```
Edit gitlab.rb to change the backup path. First, open the file in a text editor. For example: sudo nano /etc/gitlab/gitlab.rb.
Search for the line # gitlab_rails['backup_path'] = "/var/opt/gitlab/backups". If you are using nano, you can press control-w to search.
Remove the # character in front of the gitlab_rails['backup_path'] line. This will uncomment the line, making it active.
Replace the path with "/tmp/backups". The result is the following configuration line:
```
gitlab_rails['backup_path'] = "/tmp/backups"
```
Save the resulting file. If you are using nano, you can do this by pressing control-x.
Reconfigure to apply the changes.
```
sudo gitlab-ctl reconfigure
```

Task B. Backup the GitLab instance

Take a full backup of the GitLab instance.
```
sudo gitlab-backup create
```
In a production environment, you would also need to take a copy of the /etc/gitlab/gitlab.rb and /etc/gitlab/gitlab-secrets.json.
After the backup completes, go to the backup location and inspect the backup file.
```
sudo ls /tmp/backups
sudo tar -tvf /tmp/backups/<backup_filename>
```

Task C. Make some changes to GitLab settings

Sign into your GitLab instance with a web browser and open your sidebar. In the bottom left corner, click Admin area.
In the left sidebar, select Settings > General.
Expand Account and limit and change the maximum attachment size to 500 MiB, and the default project limits to 10000.
Click Save changes to save the changes.
Refresh the page and verify your changes were applied.

Task D. Restore from backup

Return to the SSH session on your GitLab instance server.
Move your backup file to the location GitLab requires for performing the restore.
```
sudo cp /tmp/backups/<backup_filename> /var/opt/gitlab/backups/
```
Ensure the backup file has correct permissions for performing the restore.
```
sudo chown git:git /var/opt/gitlab/backups/<backup_filename>
```

Stop the puma and sidekiq services before restoring.

sudo gitlab-ctl stop puma
sudo gitlab-ctl stop sidekiq
sudo gitlab-ctl status

Restore from backup. Replace <backup_timestamp> with the portion of the backup filename up to and including -ee. For example, if the backup file name starts with 1663207732_2022_09_15_15.3.3-ee, the command will be sudo gitlab-backup restore BACKUP=1663207732_2022_09_15_15.3.3-ee.
```
sudo gitlab-backup restore BACKUP=<backup_timestamp>
```
Type yes when prompted during the restore operation. You may see what looks like error messages. That is normal.
When prompted to rebuild the authorized_keys file, type yes.

Restart sidekiq and puma services.

sudo gitlab-ctl start sidekiq
sudo gitlab-ctl start puma
sudo gitlab-ctl status

Wait up to 5 minutes before refreshing GitLab in your web browser. Verify that the maximum attachment size and the default project limits you changed revert back to the defaults (i.e. when the backup was taken).

Lab Guide Complete

You have completed this lab exercise. You can view the other lab guides for this course.

Suggestions?

If you’d like to suggest changes to the GitLab System Admin Basics Hands-on Guide, please submit them via merge request.

Last modified November 14, 2024: Updating names (23df6bff)

View page source - Edit this page - please contribute.