Commit 6a5cced6 authored by Rémy Coutable's avatar Rémy Coutable

Merge branch 'patch-3' into 'master'

Emphasize that GitLab must be partially running when restoring backups.

This caused me a lot of pain until I caught on.
I also enhanced the GitLab Omnibus application data backup restore procedure.  I verified the procedure by executing it with GitLab 8.6.4.

See merge request !3844
parents 31c10e03 70351227
...@@ -295,36 +295,49 @@ Deleting tmp directories...[DONE] ...@@ -295,36 +295,49 @@ Deleting tmp directories...[DONE]
### Omnibus installations ### Omnibus installations
We will assume that you have installed GitLab from an omnibus package and run This procedure assumes that:
`sudo gitlab-ctl reconfigure` at least once.
First make sure your backup tar file is in `/var/opt/gitlab/backups` (or wherever `gitlab_rails['backup_path']` points to). - You have installed the exact same version of GitLab Omnibus with which the
backup was created
- You have run `sudo gitlab-ctl reconfigure` at least once
- GitLab is running. If not, start it using `sudo gitlab-ctl start`.
First make sure your backup tar file is in the backup directory described in the
`gitlab.rb` configuration `gitlab_rails['backup_path']`. The default is
`/var/opt/gitlab/backups`.
```shell ```shell
sudo cp 1393513186_gitlab_backup.tar /var/opt/gitlab/backups/ sudo cp 1393513186_gitlab_backup.tar /var/opt/gitlab/backups/
``` ```
Next, restore the backup by running the restore command. You need to specify the Stop the processes that are connected to the database. Leave the rest of GitLab
timestamp of the backup you are restoring. running:
```shell ```shell
# Stop processes that are connected to the database
sudo gitlab-ctl stop unicorn sudo gitlab-ctl stop unicorn
sudo gitlab-ctl stop sidekiq sudo gitlab-ctl stop sidekiq
# Verify
sudo gitlab-ctl status
```
Next, restore the backup, specifying the timestamp of the backup you wish to
restore:
```shell
# This command will overwrite the contents of your GitLab database! # This command will overwrite the contents of your GitLab database!
sudo gitlab-rake gitlab:backup:restore BACKUP=1393513186 sudo gitlab-rake gitlab:backup:restore BACKUP=1393513186
```
# Start GitLab Restart and check GitLab:
sudo gitlab-ctl start
# Check GitLab ```shell
sudo gitlab-ctl start
sudo gitlab-rake gitlab:check SANITIZE=true sudo gitlab-rake gitlab:check SANITIZE=true
``` ```
If there is a GitLab version mismatch between your backup tar file and the installed If there is a GitLab version mismatch between your backup tar file and the installed
version of GitLab, the restore command will abort with an error. Install a package for version of GitLab, the restore command will abort with an error. Install the
the [required version](https://www.gitlab.com/downloads/archives/) and try again. [correct GitLab version](https://www.gitlab.com/downloads/archives/) and try again.
## Configure cron to make daily backups ## Configure cron to make daily backups
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment