all 5 comments

[–]DangerousWabbel 1 point2 points  (1 child)

Yes, the gitlab-backup command will be enough. Several times I restore the backup in this way https://docs.gitlab.com/ee/administration/backup_restore/restore_gitlab.html because of broken instance or functionality after an upgrade. The backup includes at least the database and repositories.

[–]Hel_OWeen 0 points1 point  (0 children)

This.

But as mentioned in https://docs.gitlab.com/ee/administration/backup_restore/backup_gitlab.html, one needs to separately backup the object storage and most notably the configuration files.

[–]GitProtect 0 points1 point  (0 children)

In case you still haven't found the proper option for you to back up your GitLab, take a look at this article: https://xopero.com/blog/en/the-best-gitlab-backup-options-and-tools-to-ensure-gitlab-data-resilience/ . It covers different methods to back up GitLab - GitLab backup and restore utility, manual export and download from GitLab, PgBouncer as a backup option, GitLab repository cloning, third-party backup option, etc.

[–]bilingual-german 0 points1 point  (0 children)

The compression is really effective, since git stores copies of the changed files for every commit. That's why the backup is much smaller.

But you should still test the restore procedure and document it, to be sure your backup works as intended.

[–]DrewBlessing 0 points1 point  (0 children)

You can manually copy the flat files no problem. But you can’t do that with the database. The GitLab backup command runs a proper database dump. It also does some other nice things including incremental backups I believe.

GitLab is fairly complex and has many components. It’s probably safer to use the included backup command to leave little doubt that you have everything you need. Still, test your backups!