@@ -1172,7 +1172,7 @@ For manually backing up the Git repository data on disk, there are multiple poss
Git repositories must be copied in a consistent way. They should not be copied during concurrent write
operations, as this can lead to inconsistencies or corruption issues. For more details,
[issue 270422](https://gitlab.com/gitlab-org/gitlab/-/issues/270422"Provide documentation on preferred method of migrating Gitaly servers")
[issue #270422](https://gitlab.com/gitlab-org/gitlab/-/issues/270422"Provide documentation on preferred method of migrating Gitaly servers")
has a longer discussion explaining the potential problems.
To prevent writes to the Git repository data, there are two possible approaches:
...
...
@@ -1517,7 +1517,7 @@ err.message="unknown error"
This issue is caused by the restore running as the unprivileged user `git`,
which is unable to assign the correct ownership to the registry files during
the restore process ([issue 62759](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/62759"Incorrect permissions on registry filesystem after restore")).
the restore process ([issue #62759](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/62759"Incorrect permissions on registry filesystem after restore")).
To get your registry working again:
...
...
@@ -1548,7 +1548,7 @@ If this happens, examine the following:
- If NFS is being used, check if the mount option `timeout` is set. The
default is `600`, and changing this to smaller values results in this error.
### `gitaly-backup` for repository backup and restore **(FREE SELF)**
### `gitaly-backup` for repository backup and restore
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/333034) in GitLab 14.2.
> - [Deployed behind a feature flag](../user/feature_flags.md), enabled by default.
