diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-19 00:10:47 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-19 00:10:47 +0300 |
| commit | 355a4a17ebbeb246e48954462163577ae77f45c0 (patch) | |
| tree | 81aac8e172af511d87fcb9541508f69508bede84 /doc/administration/backup_restore | |
| parent | 7488eeff6fdf82ee7b926d684a201212b0509cbb (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/backup_restore')
| -rw-r--r-- | doc/administration/backup_restore/index.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/administration/backup_restore/index.md b/doc/administration/backup_restore/index.md index 89b71a7c621..72a0176adc1 100644 --- a/doc/administration/backup_restore/index.md +++ b/doc/administration/backup_restore/index.md @@ -42,7 +42,7 @@ a non-packaged Redis instance, or non-packaged Sidekiq. Prerequisites: - Some time before your migration, consider notifying your users of upcoming - scheduled maintenance with a [broadcast message banner](../../user/admin_area/broadcast_messages.md). + scheduled maintenance with a [broadcast message banner](../broadcast_messages.md). - Ensure your backups are complete and current. Create a complete system-level backup, or take a snapshot of all servers involved in the migration, in case destructive commands (like `rm`) are run incorrectly. @@ -214,7 +214,7 @@ To prepare the new server: sudo gitlab-ctl reconfigure ``` -1. Remove the scheduled maintenance [broadcast message banner](../../user/admin_area/broadcast_messages.md). +1. Remove the scheduled maintenance [broadcast message banner](../broadcast_messages.md). ## Additional notes |