From 4743b8bd6a6c1556c1a3163b438de90360e2e374 Mon Sep 17 00:00:00 2001 From: karen Carias Date: Tue, 8 Sep 2015 18:36:11 -0700 Subject: [PATCH 1/2] link to rake tasks --- doc/raketasks/backup_restore.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index 6a68c8e8286..b0ea1a97535 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -7,7 +7,9 @@ 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. The best way to migrate your repositories from one server to another is through backup restore. +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 @@ -370,3 +372,6 @@ For more information see similar questions on postgresql issue tracker[here](htt ## Note This documentation is for GitLab CE. We backup GitLab.com and make sure your data is secure, but you can't use these methods to export / backup your data yourself from GitLab.com. + +To migrate your repositories from one server to another with an up-to-date version of +GitLab, you can use [rake tasks](import.md) to do a mass import of the repository. From 6a1d695f861e4c5251a2333c673f78705b34891f Mon Sep 17 00:00:00 2001 From: karen Carias Date: Wed, 9 Sep 2015 15:17:41 -0700 Subject: [PATCH 2/2] made info more clear --- doc/raketasks/backup_restore.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index b0ea1a97535..ad1914398d6 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -374,4 +374,6 @@ This documentation is for GitLab CE. We backup GitLab.com and make sure your data is secure, but you can't use these methods to export / backup your data yourself from GitLab.com. To migrate your repositories from one server to another with an up-to-date version of -GitLab, you can use [rake tasks](import.md) to do a mass import of the repository. +GitLab, you can use the [import rake task](import.md) to do a mass import of the +repository. Note that if you do an import rake task, rather than a backup restore, you +will have all your repositories, but not any other data.