diff options
Diffstat (limited to 'doc/update/plan_your_upgrade.md')
| -rw-r--r-- | doc/update/plan_your_upgrade.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/update/plan_your_upgrade.md b/doc/update/plan_your_upgrade.md index 9378b104c81..634c430e251 100644 --- a/doc/update/plan_your_upgrade.md +++ b/doc/update/plan_your_upgrade.md @@ -11,7 +11,7 @@ GitLab instance. General notes: -- If possible, we recommend you test out the upgrade in a test environment before +- If possible, you should test out the upgrade in a test environment before updating your production instance. Ideally, your test environment should mimic your production environment as closely as possible. - If [working with Support](https://about.gitlab.com/support/scheduling-upgrade-assistance/) @@ -75,25 +75,25 @@ Create a backup of GitLab and all its data (database, repositories, uploads, bui artifacts, LFS objects, registry, pages). This is vital for making it possible to roll back GitLab to a working state if there's a problem with the upgrade: -- Create a [GitLab backup](../raketasks/backup_restore.md). +- Create a [GitLab backup](../administration/backup_restore/index.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_gitlab.md#storing-configuration-files). + Don't forget to back up the [secrets and configuration files](../administration/backup_restore/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.** ### Restore GitLab -If you have a test environment that mimics your production one, we recommend testing the restoration to ensure that everything works as you expect. +If you have a test environment that mimics your production one, you should test the restoration to ensure that everything works as you expect. To restore your GitLab backup: - Before restoring, make sure to read about the - [prerequisites](../raketasks/backup_restore.md#restore-gitlab), most importantly, + [prerequisites](../administration/backup_restore/index.md#restore-gitlab), most importantly, the versions of the backed up and the new GitLab instance must be the same. -- [Restore GitLab](../raketasks/backup_restore.md#restore-gitlab). +- [Restore GitLab](../administration/backup_restore/index.md#restore-gitlab). Make sure to follow the instructions based on your installation method. - Confirm that the [secrets and configuration files](../raketasks/backup_gitlab.md#storing-configuration-files) are also restored. + Confirm that the [secrets and configuration files](../administration/backup_restore/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.** |