diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-09 09:13:16 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-09 09:13:16 +0000 |
| commit | ece36a21699c2a218b8bd14b22bea47d22218354 (patch) | |
| tree | 8e08e12d70ead67a9b1f6951d29661463fda6387 /doc/raketasks | |
| parent | e168d3919a2c82eafa1d1f81e4b96aedae28717a (diff) | |
| download | gitlab-ce-ece36a21699c2a218b8bd14b22bea47d22218354.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/raketasks')
| -rw-r--r-- | doc/raketasks/restore_gitlab.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/raketasks/restore_gitlab.md b/doc/raketasks/restore_gitlab.md index 30395c36c91..2f38cbe2545 100644 --- a/doc/raketasks/restore_gitlab.md +++ b/doc/raketasks/restore_gitlab.md @@ -29,12 +29,11 @@ restore. This is because the system user performing the restore actions (`git`) is usually not allowed to create or delete the SQL database needed to import data into (`gitlabhq_production`). All existing data is either erased (SQL) or moved to a separate directory (such as repositories and uploads). +Restoring SQL data skips views owned by PostgreSQL extensions. To restore a backup, **you must also restore the GitLab secrets**. - These include the database encryption key, [CI/CD variables](../ci/variables/index.md), and variables used for [two-factor authentication](../user/profile/account/two_factor_authentication.md). - Without the keys, [multiple issues occur](backup_restore.md#when-the-secrets-file-is-lost), including loss of access by users with [two-factor authentication enabled](../user/profile/account/two_factor_authentication.md), and GitLab Runners cannot log in. |