diff options
author | Evan Read <eread@gitlab.com> | 2018-11-29 07:59:12 +0300 |
---|---|---|
committer | Evan Read <eread@gitlab.com> | 2018-11-29 07:59:12 +0300 |
commit | a5f4627857bddc7e431d0fca6f17560e4b07e0b9 (patch) | |
tree | 43219353cb28fdb6f92894b16e6642d0377d7f34 | |
parent | 14b7b0d90070923e3ca14920a59984866cbc722a (diff) | |
parent | d34e4ba91b41e6d02dc2eb7504560ba056822d66 (diff) |
Merge branch 'restore-ssh-host-keys' into 'master'
Update documentation with note regarding restoring ssh host keys
See merge request gitlab-org/gitlab-ce!23392
-rw-r--r-- | doc/raketasks/backup_restore.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index 18c9cd116f1..a63656fafef 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -604,6 +604,8 @@ If you fail to restore this encryption key file along with the application data backup, users with two-factor authentication enabled and GitLab Runners will lose access to your GitLab server. +You may also want to restore any TLS keys, certificates, or [SSH host keys](https://superuser.com/questions/532040/copy-ssh-keys-from-one-server-to-another-server/532079#532079). + Depending on your case, you might want to run the restore command with one or more of the following options: |