Gitlab migration steps


I have a “GitLab Omnibus Community Edition” installed on centos 7. Repositories are stored on the second mounted volume (/volume/repositories). Also, I use Apache-v.2.4.6.

Now, I want to migrate GitLab to the new separate “Amazon Linux AMI server (centos 6)” and use all GitLab’s features like nginx instead of apache.

But I’m afraid of missing something while migrating to a new server.
Could you, please help me to check migration steps?

GitLab migration steps:

On the old server with apache:

  1. Create backup: sudo gitlab-rake gitlab:backup:create SKIP=repositories

  2. Detach volume from the old instance (with “/volume/repositories” folder)

  3. Copy backup “tar” file to the new instance (into /var/opt/gitlab/backups)

On the new server:

  1. Attach volume from the old instance to the new instance (with “/volume/repositories” folder)

  2. chown -R git:git /volume/repositories/

  3. sudo yum install -y curl policycoreutils-python openssh-server cronie (should be the same version of GitLab)

  4. sudo lokkit -s http -s ssh (sudo: lokkit: command not found and I don’t know if this command should be)

  5. curl | sudo bash

  6. sudo EXTERNAL_URL=“” yum -y install gitlab-ce

  7. sudo gitlab-ctl stop unicorn

  8. sudo gitlab-ctl stop sidekiq

  9. sudo gitlab-rake gitlab:backup:restore BACKUP=backup-file-folder

  10. copy and replace “gitlab-secrets.json”, “trusted-certs” folder, “gitlab.rb” - to /etc/gitlab/

  11. In “gitlab.rb” file - check the path to repositories, disable apache, enable nginx and check other settings.

  12. sudo gitlab-ctl reconfigure

  13. sudo gitlab-ctl restart

  14. sudo gitlab-rake gitlab:check SANITIZE=true

  15. after “gitlab-ctl reconfigure” command, folder: /var/opt/gitlab/ will be reconfigured according to the “gitlab.rb” file settings.