Gitlab Restore Freeze after unpack backup


#1

Hi All,

I’m having an Issue while backing up and restoring company gitlab on a docker.
I’m running version “GitLab Community Edition 10.6.2” on a docker “gitlab/gitlab-ce:10.6.2-ce.0”

I used the following command to backup:

docker exec -t <container name> gitlab-rake gitlab:backup:create

Example output:

Dumping database tables:
- Dumping table events... [DONE]
- Dumping table issues... [DONE]
- Dumping table keys... [DONE]
- Dumping table merge_requests... [DONE]
- Dumping table milestones... [DONE]
- Dumping table namespaces... [DONE]
- Dumping table notes... [DONE]
- Dumping table projects... [DONE]
- Dumping table protected_branches... [DONE]
- Dumping table schema_migrations... [DONE]
- Dumping table services... [DONE]
- Dumping table snippets... [DONE]
- Dumping table taggings... [DONE]
- Dumping table tags... [DONE]
- Dumping table users... [DONE]
- Dumping table users_projects... [DONE]
- Dumping table web_hooks... [DONE]
- Dumping table wikis... [DONE]
Dumping repositories:
- Dumping repository abcd... [DONE]
Creating backup archive: $TIMESTAMP_gitlab_backup.tar [DONE]
Deleting tmp directories...[DONE]
Deleting old backups... [SKIPPING]

After the final tar is created, moved it to the new debian server with docker and same folder structure than the origin one.

Then, start the new docker compose and run the following procedure to restore:

docker exec -t gitlab_web_1 gitlab-ctl stop unicorn
docker exec -t gitlab_web_1 gitlab-ctl stop sidekiq
docker exec -t gitlab_web_1 gitlab-ctl status

OUTPUT:

run: gitaly: (pid 759) 927s; run: log: (pid 744) 927s
run: gitlab-monitor: (pid 762) 927s; run: log: (pid 748) 927s
run: gitlab-pages: (pid 760) 927s; run: log: (pid 747) 927s
run: gitlab-workhorse: (pid 769) 927s; run: log: (pid 752) 927s
run: logrotate: (pid 756) 927s; run: log: (pid 742) 927s
run: nginx: (pid 765) 927s; run: log: (pid 750) 927s
run: node-exporter: (pid 757) 927s; run: log: (pid 741) 927s
run: postgres-exporter: (pid 766) 927s; run: log: (pid 751) 927s
run: postgresql: (pid 767) 927s; run: log: (pid 753) 927s
run: prometheus: (pid 768) 927s; run: log: (pid 754) 927s
run: redis: (pid 764) 927s; run: log: (pid 749) 927s
run: redis-exporter: (pid 758) 927s; run: log: (pid 745) 927s
down: sidekiq: 9s, normally up; run: log: (pid 743) 927s
run: sshd: (pid 21) 962s; run: log: (pid 20) 962s
down: unicorn: 17s, normally up; run: log: (pid 746) 927s

Then:

docker exec -t gitlab_web_1 gitlab-rake gitlab:backup:restore BACKUP="backupfilename"

It starts Unpacking, i’m able to see the files showing up on the backup folder and all the files are unpacked.

Unpacking backup ... done

The problem appear now, the following message is shown:

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

After click yes it does not start doing anything and does not give any error.
Just stays stopped forever.

Any ideas?
I’m I doing something wrong or is there any known issue?

Hope i get some help on this.

Very Best,
Emanuel Guerra


#2

Hi,

Can you add the -i argument and try again?

ex:

docker exec -it …

or entering the same container

docker exec -it gitlab_web_1 /bin/bash

and then

gitlab-rake gitlab:backup:restore BACKUP=“backupfilename”


#3

Hi,

Thank you for your reply.

It seems to be working on my test server. I will try it now on my official server but it will take a few hours to unpack. I’ll let u know if it work with a lot of data too.

What does the “-i” argument do?

Very Best,
Emanuel Guerra


#4

Excelente, me alegro.

Well, When establishing a connection, the connection is kept open to interact (-i), in this case it is known as stdin


#5

Hi,

Worded, thank you very much once again.


#6

Great!, You are Welcome