Commit 207b60084233e23133aad99f3857105d2c52e9aa
1 parent
ec8a6877
Exists in
master
and in
13 other branches
Include PG workaround in restore instructions
Showing
1 changed file
with
9 additions
and
0 deletions
Show diff stats
README.md
... | ... | @@ -116,8 +116,17 @@ Next, restore the backup by running the restore command. You need to specify the |
116 | 116 | timestamp of the backup you are restoring. |
117 | 117 | |
118 | 118 | ```shell |
119 | +# Stop processes that are connected to the database | |
120 | +sudo gitlab-ctl stop unicorn | |
121 | +sudo gitlab-ctl stop sidekiq | |
122 | + | |
123 | +# DROP THE CURRENT DATABASE; workaround for a Postgres backup restore bug in GitLab 6.6 | |
124 | +sudo -u gitlab-psql /opt/gitlab/embedded/bin/dropdb gitlabhq_production | |
119 | 125 | # This command will overwrite the contents of your GitLab database! |
120 | 126 | sudo gitlab-rake gitlab:backup:restore BACKUP=1393513186 |
127 | + | |
128 | +# Start GitLab | |
129 | +sudo gitlab-ctl start | |
121 | 130 | ``` |
122 | 131 | |
123 | 132 | If there is a GitLab version mismatch between your backup tar file and the installed | ... | ... |