GitLab Documentation

GitLab Geo Disaster Recovery

Note: GitLab Geo Disaster Recovery is in Alpha development. Please don't use as your only Disaster Recovery strategy as you may lose data.

GitLab Geo replicates your database and your Git repositories. We will support and replicate more data in the future, that will enable you to fail-over with minimal effort, in a disaster situation.

See current limitations for more information.

Promoting a secondary node

We don't provide yet an automated way to promote a node and do fail-over, but you can do it manually if you have root access to the machine.

You must make the changes in the exact specific order:

  1. Take down your primary node (or make sure it will not go up during this process or you may lose data)
  2. Wait for any database replication to finish
  3. Modify the gitlab.rb for both nodes to reflect their new statuses
  4. Log-in to your secondary node with a user with sudo permission
  5. Run sudo gitlab-ctl promote-to-primary-node

To bring your old primary node back into use as a working secondary, you need to run gitlab-ctl reconfigure against the node and then follow the setup instructions again, as if for a secondary node, from step 3.

Leave a comment below if you have any feedback on the documentation. For support and other inquires, see getting help.