diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-04-06 12:09:21 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-04-06 12:09:21 +0000 |
| commit | ebed39e3cedad74e1a1ee4e8d33adfb8bbdc7040 (patch) | |
| tree | ae91160251c527eb063413ff9e530b6da96eb74d /doc/update | |
| parent | 61ee5c363522f2639d1c515a74b9b02b7672c7c2 (diff) | |
| download | gitlab-ce-ebed39e3cedad74e1a1ee4e8d33adfb8bbdc7040.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/update')
| -rw-r--r-- | doc/update/restore_after_failure.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/update/restore_after_failure.md b/doc/update/restore_after_failure.md index 64e92c802f2..6da9f11509a 100644 --- a/doc/update/restore_after_failure.md +++ b/doc/update/restore_after_failure.md @@ -12,7 +12,8 @@ However, it's important to know how to recover when problems do arise. ## Roll back to an earlier version and restore a backup In some cases after a failed upgrade, the fastest solution is to roll back to -the previous version you were using. +the previous version you were using. We recommend this path because the failed +upgrade will likely have made database changes that can not be readily reverted. First, roll back the code or package. For source installations this involves checking out the older version (branch or tag). For Omnibus installations this |