diff options
author | karen Carias <karen@gitlab.com> | 2015-08-04 14:51:08 -0700 |
---|---|---|
committer | karen Carias <karen@gitlab.com> | 2015-08-04 14:51:08 -0700 |
commit | b83b3332171f7de1046b5e27a1351daf84fac583 (patch) | |
tree | c6bc9112c7364618100473b07da2d2083c17fc9e | |
parent | 326b827ce39f998ce75f58e9f649e6b50623f1aa (diff) | |
download | gitlab-ce-b83b3332171f7de1046b5e27a1351daf84fac583.tar.gz |
added note about changing servers
-rw-r--r-- | doc/raketasks/backup_restore.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index 05324b33022..d704d93fdef 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -7,7 +7,7 @@ A backup creates an archive file that contains the database, all repositories and all attachments. This archive will be saved in backup_path (see `config/gitlab.yml`). The filename will be `[TIMESTAMP]_gitlab_backup.tar`. This timestamp can be used to restore an specific backup. -You can only restore a backup to exactly the same version of GitLab that you created it on, for example 7.2.1. +You can only restore a backup to exactly the same version of GitLab that you created it on, for example 7.2.1. The best way to migrate your repositories from one server to another is through backup restore. You need to keep a separate copy of `/etc/gitlab/gitlab-secrets.json` (for omnibus packages) or `/home/git/gitlab/.secret` (for installations |