diff options
Diffstat (limited to 'doc/update/plan_your_upgrade.md')
| -rw-r--r-- | doc/update/plan_your_upgrade.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/update/plan_your_upgrade.md b/doc/update/plan_your_upgrade.md index cdc3ec39f9a..2374856ff0c 100644 --- a/doc/update/plan_your_upgrade.md +++ b/doc/update/plan_your_upgrade.md @@ -87,7 +87,7 @@ to roll back GitLab to a working state if there's a problem with the upgrade: - Create a [GitLab backup](../raketasks/backup_restore.md). Make sure to follow the instructions based on your installation method. - Don't forget to back up the [secrets and configuration files](../raketasks/backup_restore.md#storing-configuration-files). + Don't forget to back up the [secrets and configuration files](../raketasks/backup_gitlab.md#storing-configuration-files). - Alternatively, create a snapshot of your instance. If this is a multi-node installation, you must snapshot every node. **This process is out of scope for GitLab Support.** @@ -103,7 +103,7 @@ To restore your GitLab backup: the versions of the backed up and the new GitLab instance must be the same. - [Restore GitLab](../raketasks/backup_restore.md#restore-gitlab). Make sure to follow the instructions based on your installation method. - Confirm that the [secrets and configuration files](../raketasks/backup_restore.md#storing-configuration-files) are also restored. + Confirm that the [secrets and configuration files](../raketasks/backup_gitlab.md#storing-configuration-files) are also restored. - If restoring from a snapshot, know the steps to do this. **This process is out of scope for GitLab Support.** |