Commit 3c5190aa authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'docs-avoid-anchoring-below-backup-version-advice' into 'master'

Anchor backup hyperlinks above version advice

See merge request gitlab-org/gitlab!71267
parents 3f8d1a6e 7a6054b6
...@@ -128,7 +128,7 @@ The routine differs, depending on whether you deployed with Omnibus or the Helm ...@@ -128,7 +128,7 @@ The routine differs, depending on whether you deployed with Omnibus or the Helm
When you backing up an Omnibus (single node) GitLab server, you can use a single Rake task. When you backing up an Omnibus (single node) GitLab server, you can use a single Rake task.
Learn about [backing up Omnibus or Helm variations](../raketasks/backup_restore.md#back-up-gitlab). Learn about [backing up Omnibus or Helm variations](../raketasks/backup_restore.md).
This process backs up your entire instance, but does not back up the configuration files. Ensure those are backed up separately. 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. Keep your configuration files and backup archives in a separate location to ensure the encryption keys are not kept with the encrypted data.
......
...@@ -1075,7 +1075,7 @@ GitLab also tracks [Prometheus metrics for Praefect](gitaly/#monitor-gitaly-clus ...@@ -1075,7 +1075,7 @@ GitLab also tracks [Prometheus metrics for Praefect](gitaly/#monitor-gitaly-clus
For Omnibus installations, the backup log is located at `/var/log/gitlab/gitlab-rails/backup_json.log`. For Omnibus installations, the backup log is located at `/var/log/gitlab/gitlab-rails/backup_json.log`.
This log is populated when a [GitLab backup is created](../raketasks/backup_restore.md#back-up-gitlab). You can use this log to understand how the backup process performed. This log is populated when a [GitLab backup is created](../raketasks/backup_restore.md). You can use this log to understand how the backup process performed.
## Performance bar stats ## Performance bar stats
......
...@@ -66,7 +66,7 @@ sudo gitlab-ctl start puma ...@@ -66,7 +66,7 @@ sudo gitlab-ctl start puma
If you want to allow users to use the GitLab UI, then you'll need to ensure that If you want to allow users to use the GitLab UI, then you'll need to ensure that
the database is read-only: the database is read-only:
1. Take a [GitLab backup](../raketasks/backup_restore.md#back-up-gitlab) 1. Take a [GitLab backup](../raketasks/backup_restore.md)
in case things don't go as expected. in case things don't go as expected.
1. Enter PostgreSQL on the console as an administrator user: 1. Enter PostgreSQL on the console as an administrator user:
......
...@@ -748,7 +748,7 @@ Read more on configuring an ...@@ -748,7 +748,7 @@ Read more on configuring an
## Backup and restore ## Backup and restore
GitLab provides [a tool to back up](../../raketasks/backup_restore.md#back-up-gitlab) GitLab provides [a tool to back up](../../raketasks/backup_restore.md)
and restore its Git data, database, attachments, LFS objects, and so on. and restore its Git data, database, attachments, LFS objects, and so on.
Some important things to know: Some important things to know:
......
...@@ -175,7 +175,7 @@ sudo gitlab-psql -d mattermost_production ...@@ -175,7 +175,7 @@ sudo gitlab-psql -d mattermost_production
### Back up GitLab Mattermost ### Back up GitLab Mattermost
GitLab Mattermost is not included in the regular [Omnibus GitLab backup](../../raketasks/backup_restore.md#back-up-gitlab) Rake task. GitLab Mattermost is not included in the regular [Omnibus GitLab backup](../../raketasks/backup_restore.md) Rake task.
The general Mattermost [backup and disaster recovery](https://docs.mattermost.com/deploy/backup-disaster-recovery.html) documentation can be used as a guide The general Mattermost [backup and disaster recovery](https://docs.mattermost.com/deploy/backup-disaster-recovery.html) documentation can be used as a guide
on what needs to be backed up. on what needs to be backed up.
......
...@@ -12,7 +12,7 @@ of a package. ...@@ -12,7 +12,7 @@ of a package.
WARNING: WARNING:
You must at least have a database backup created under the version you are You must at least have a database backup created under the version you are
downgrading to. Ideally, you should have a downgrading to. Ideally, you should have a
[full backup archive](../../raketasks/backup_restore.md#back-up-gitlab) [full backup archive](../../raketasks/backup_restore.md)
on hand. on hand.
The example below demonstrates the downgrade procedure when downgrading between minor The example below demonstrates the downgrade procedure when downgrading between minor
......
...@@ -75,7 +75,7 @@ Create a backup of GitLab and all its data (database, repos, uploads, builds, ...@@ -75,7 +75,7 @@ Create a backup of GitLab and all its data (database, repos, uploads, builds,
artifacts, LFS objects, registry, pages). This is vital for making it possible 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: to roll back GitLab to a working state if there's a problem with the upgrade:
- Create a [GitLab backup](../raketasks/backup_restore.md#back-up-gitlab). - Create a [GitLab backup](../raketasks/backup_restore.md).
Make sure to follow the instructions based on your installation method. 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_restore.md#storing-configuration-files).
- Alternatively, create a snapshot of your instance. If this is a multi-node - Alternatively, create a snapshot of your instance. If this is a multi-node
......
...@@ -212,7 +212,7 @@ that are not in status **closed** from one project to another. ...@@ -212,7 +212,7 @@ that are not in status **closed** from one project to another.
To access rails console run `sudo gitlab-rails console` on the GitLab server and run the below To access rails console run `sudo gitlab-rails console` on the GitLab server and run the below
script. Please be sure to change `project`, `admin_user`, and `target_project` to your values. script. Please be sure to change `project`, `admin_user`, and `target_project` to your values.
We do also recommend [creating a backup](../../../raketasks/backup_restore.md#back-up-gitlab) before We do also recommend [creating a backup](../../../raketasks/backup_restore.md) before
attempting any changes in the console. attempting any changes in the console.
```ruby ```ruby
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment