diff options
| author | Bob Van Landuyt <bob@vanlanduyt.co> | 2018-04-19 12:44:15 +0300 |
|---|---|---|
| committer | Bob Van Landuyt <bob@vanlanduyt.co> | 2018-04-23 18:24:29 +0300 |
| commit | effda09e06997f3b800e56617e1200cf795b890d (patch) | |
| tree | 02382267308755896b4387cf23897c599ec22026 /doc/raketasks | |
| parent | c212908aad9b32352653dfe9ca966f148c8dfc1a (diff) | |
Suggest place for data-directories on mountpoints
Using a mountpoint as data directory causes issues when restoring, so
we need to mention this in the documentation.
Diffstat (limited to 'doc/raketasks')
| -rw-r--r-- | doc/raketasks/backup_restore.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index bbd2d214fe4..785cc32d590 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -498,6 +498,13 @@ more of the following options: Read what the [backup timestamp is about](#backup-timestamp). - `force=yes` - Does not ask if the authorized_keys file should get regenerated and assumes 'yes' for warning that database tables will be removed. +If you are restoring into directories that are mountpoints you will need to make +sure these directories are empty before attempting a restore. Otherwise GitLab +will attempt to move these directories before restoring the new data and this +would cause an error. + +Read more on [configuring NFS mounts](../administration/high_availability/nfs.md) + ### Restore for installation from source ``` |