diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-04-20 13:00:54 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-04-20 13:00:54 +0300 |
commit | 3cccd102ba543e02725d247893729e5c73b38295 (patch) | |
tree | f36a04ec38517f5deaaacb5acc7d949688d1e187 /doc/administration/geo/disaster_recovery/planned_failover.md | |
parent | 205943281328046ef7b4528031b90fbda70c75ac (diff) |
Add latest changes from gitlab-org/gitlab@14-10-stable-eev14.10.0-rc42
Diffstat (limited to 'doc/administration/geo/disaster_recovery/planned_failover.md')
-rw-r--r-- | doc/administration/geo/disaster_recovery/planned_failover.md | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/administration/geo/disaster_recovery/planned_failover.md b/doc/administration/geo/disaster_recovery/planned_failover.md index 939b4aec968..2a21bda23d7 100644 --- a/doc/administration/geo/disaster_recovery/planned_failover.md +++ b/doc/administration/geo/disaster_recovery/planned_failover.md @@ -42,6 +42,38 @@ Repository-centric strategies for using `rsync` effectively can be found in the [moving repositories](../../operations/moving_repositories.md) documentation; these strategies can be adapted for use with any other file-based data, such as [GitLab Pages](../../pages/index.md#change-storage-path). +### Container registry + +By default, the container registry is not automatically replicated to secondary +sites and this needs to be manually configured, see [Docker Registry for a secondary site](../replication/docker_registry.md). + +If you are using local storage on your current primary site for the container +registry, you can `rsync` the container registry objects to the secondary +site you are about to failover to: + +```shell +# Run from the secondary site +rsync --archive --perms --delete root@<geo-primary>:/var/opt/gitlab/gitlab-rails/shared/registry/. /var/opt/gitlab/gitlab-rails/shared/registry +``` + +Alternatively, you can [back up](../../../raketasks/backup_restore.md#back-up-gitlab) +the container registry on the primary site and restore it onto the secondary +site: + +1. On your primary site, back up only the registry and [exclude specific directories +from the backup](../../../raketasks/backup_restore.md#excluding-specific-directories-from-the-backup): + + ```shell + # Create a backup in the /var/opt/gitlab/backups folder + sudo gitlab-backup create SKIP=db,uploads,builds,artifacts,lfs,terraform_state,pages,repositories,packages + ``` + +1. Copy the backup tarball generated from your primary site to the `/var/opt/gitlab/backups` folder +on your secondary site. + +1. On your secondary site, restore the registry following the [Restore GitLab](../../../raketasks/backup_restore.md#restore-gitlab) +documentation. + ## Preflight checks NOTE: |