diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-28 12:10:06 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-28 12:10:06 +0300 |
| commit | 8ce5735a199949ad19db9e83544875cd81562c69 (patch) | |
| tree | d552cb10b20be7d301adc094f770f76a1528de80 /doc/administration/get_started.md | |
| parent | e9a3e8b891637a79ff6cc5bef9762272f312f04d (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/get_started.md')
| -rw-r--r-- | doc/administration/get_started.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/administration/get_started.md b/doc/administration/get_started.md index 60291732a20..b4c7a7be18c 100644 --- a/doc/administration/get_started.md +++ b/doc/administration/get_started.md @@ -130,7 +130,7 @@ The routine differs, depending on whether you deployed with the Linux package or When backing up (single node) GitLab server installed using the Linux package, you can use a single Rake task. -Learn about [backing up Linux package or Helm variations](../raketasks/backup_restore.md). +Learn about [backing up Linux package or Helm variations](../administration/backup_restore/index.md). This process backs up your entire instance, but does not back up the configuration files. Ensure those are backed up separately. Keep your configuration files and backup archives in a separate location to ensure the encryption keys are not kept with the encrypted data. @@ -163,7 +163,7 @@ For more information about GitLab SaaS backups, see our [Backup FAQ page](https: ### Alternative backup strategies In some situations the Rake task for backups may not be the most optimal solution. Here are some -[alternatives](../raketasks/backup_restore.md) to consider if the Rake task does not work for you. +[alternatives](../administration/backup_restore/index.md) to consider if the Rake task does not work for you. #### Option 1: File system snapshot |