Errors when doing backup and restore to new Server

How to Use GitLab
1

Hi Everyone,

I’m planning on doing a backup and restore for an OS upgrade from AL1 to AMZ2023

But unfortunately I’m running on to an obstacle.

I’ve been having some permission error when restoring gitlab postgre database giving out ownership issues. D

Transfering ownership of /var/opt/gitlab/gitlab-rails/shared/registry to git
2024-11-22 02:12:52 UTC -- Unpacking backup ...
2024-11-22 02:28:24 UTC -- Unpacking backup ... done
2024-11-22 02:28:24 UTC -- Restoring database ...
2024-11-22 02:28:24 UTC -- Be sure to stop Puma, Sidekiq, and any other process that
connects to the database before proceeding. For Omnibus
installs, see the following link for more information:
https://docs.gitlab.com/ee/raketasks/backup_restore.html#restore-for-omnibus-gitlab-installations

Before restoring the database, we will remove all existing
tables to avoid future upgrade problems. Be aware that if you have
custom tables in the GitLab database these tables and all data will be
removed.

Do you want to continue (yes/no)? yes
Removing all tables. Press `Ctrl-C` within 5 seconds to abort
2024-11-22 02:32:19 UTC -- Cleaning the database ...
2024-11-22 02:32:22 UTC -- done
Restoring PostgreSQL database gitlabhq_production ... ERROR:  must be owner of extension pg_trgm
ERROR:  must be owner of extension btree_gist
ERROR:  must be owner of extension btree_gist
ERROR:  must be owner of extension pg_trgm

Also during backup creation i’ve skipped on artifacts. Is there anyway to manually migrate this to the new server?

are these gonna be a problem?

I saw one saying it’s harmless is it true?

2

I was one of the people saying “they seem not to matter” in that thread, and while it has been a while since I did a restore (I guess I was working on or had recently finished a move back then, and when we moved to our current setup one of my colleagues did DB migrations), as long as the extensions are there, I can’t see it really matter if gitlab is the owner.

1 Like