====== Gitlab move to new instance  ======

Both source and destination Gitlab versions has to be the same.

  * Install fresh Gitlab on new machine. 
  * Make full backup on source machine

===== Restore =====

  * [[https://docs.gitlab.com/ee/raketasks/backup_restore.html#restore-for-omnibus-gitlab-installations|Restore for Omnibus GitLab installations]]

===== Issue =====

Issue:
  * users cannot connect with ssh. 
  * ''gitlab-rake check'' returns all OK
  * File ''/var/opt/gitlab/.ssh/authorized_keys'' is empty.

Solution:
  * run ''gitlab-rake gitlab:shell:setup'' to 
  * More info: [[https://docs.gitlab.com/ee/administration/raketasks/maintenance.html#rebuild-authorized_keys-file|Rebuild authorized_keys file]]

Related issues:
  * [[https://gitlab.com/gitlab-org/gitlab/-/issues/2882|authorized_keys file is not being updated, users can't use new keys and new users broken]]
  * [[https://serverfault.com/questions/772514/after-restoring-gitlab-backup-new-ssh-public-keys-randomly-supersede-other-user|After restoring GitLab backup, new SSH public keys randomly supersede other users' existing keys]]