diff options
| author | Marin Jankovski <marin@gitlab.com> | 2018-05-18 10:30:27 +0000 |
|---|---|---|
| committer | Marin Jankovski <marin@gitlab.com> | 2018-05-18 10:30:27 +0000 |
| commit | 83660e5712dde52767a0a22023785b9006b81c21 (patch) | |
| tree | 6ff04edcceef820dc220b3d1933d828a281ca256 | |
| parent | 12fa70f5fff00d72153dcfadc5712ce191ddbce8 (diff) | |
| parent | b1135b61e60654f5b3f1b68e18c40627b5fce786 (diff) | |
| download | gitlab-ce-83660e5712dde52767a0a22023785b9006b81c21.tar.gz | |
Merge branch 'docker-backup-restore-doc' into 'master'
Add doc about backup-restore in docker and k8s
Closes gitlab-org/distribution/team-tasks#87
See merge request gitlab-org/gitlab-ce!18702
| -rw-r--r-- | doc/raketasks/backup_restore.md | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index 785cc32d590..77139c50d07 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -64,6 +64,13 @@ If you are running GitLab within a Docker container, you can run the backup from docker exec -t <container name> gitlab-rake gitlab:backup:create ``` +If you are using the gitlab-omnibus helm chart on a Kubernetes cluster, you can +run the backup task on the gitlab application pod using kubectl + +``` +kubectl exec -it <gitlab-gitlab pod> gitlab-rake gitlab:backup:create +``` + Example output: ``` @@ -601,6 +608,34 @@ If there is a GitLab version mismatch between your backup tar file and the insta version of GitLab, the restore command will abort with an error. Install the [correct GitLab version](https://packages.gitlab.com/gitlab/) and try again. +### Restore for Docker image and gitlab-omnibus helm chart + +For GitLab installations using docker image or the gitlab-omnibus helm chart on +a Kubernetes cluster, restore task expects the restore directories to be empty. +However, with docker and Kubernetes volume mounts, some system level directories +may be created at the volume roots, like `lost+found` directory found in Linux +operating systems. These directories are usually owned by `root`, which can +cause access permission errors since the restore rake task runs as `git` user. +So, to restore a GitLab installation, users have to confirm the restore target +directories are empty. + +For both these installation types, the backup tarball has to be available in the +backup location (default location is `/var/opt/gitlab/backups`). + +For docker installations, the restore task can be run from host using the +command + +``` +docker exec -it <name of container> gitlab-rake gitlab:backup:restore +``` + +Similarly, for gitlab-omnibus helm chart, the restore task can be run on the +gitlab application pod using kubectl + +``` +kubectl exec -it <gitlab-gitlab pod> gitlab-rake gitlab:backup:restore +``` + ## Alternative backup strategies If your GitLab server contains a lot of Git repository data you may find the GitLab backup script to be too slow. |