Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Geo and Disaster Recovery

On this page

The Geo Team

Geo is a Premium feature, built to help speed up the development of distributed teams by providing one or more read-only mirrors of a primary GitLab instance. This mirror (a Geo secondary node) reduces the time to clone or fetch large repositories and projects, or can be part of a Disaster Recovery solution.

Team members

Person Role
Rachel Nienaber Engineering Manager, Geo
Valery Sizov Senior Backend Engineer, Geo
Gabriel Mazetto Backend Engineer, Geo
Douglas Barbosa Alexandre Senior Backend Engineer, Geo
Toon Claes Backend Engineer, Geo
Michael Kozono Senior Backend Engineer, Geo
Ash McKenzie Staff Backend Engineer, Geo

Stable counterparts

Person Role
Kushal Pandya Senior Frontend Engineer, Plan & Geo
Devin Sylva Senior Site Reliability Engineer, Package, Geo
Fabian Zimmer Senior Product Manager, Geo

Goals and Priorities

Our priorities are aligned with the product direction. You can read more about this on the Geo Product Vision page.

Alongside the items listed in our Product Vision, we need to constantly assess issues that our customers bring to our attention. These could take the form of bug reports or feature requests. Geo users are often our largest customers and some rely on Geo as a critical part of their workflow.

We also work constantly to keep housekeeping chores to a manageable level. Where possible, we address these issues as part of a related project. Where this is not possible, we use time around our projects to make this happen.

Geo's Relationship to Disaster Recovery

Disaster Recovery (DR) is a set of policies, tools and procedures put in place to be able to recover from a disaster.

Geo provides data redundancy. The customer will have a redundant copy of data in a separate location. If anything were to happen to their primary instance, a secondary instance still retains a copy of the data.

However, data redundancy is one part of a complete DR strategy.

High Availability (HA) is also a step towards Disaster Recovery. At the moment Geo does not provide true HA because if the primary instance is not available, certain actions are not possible.

Documentation

Other Resources

Geo Terminology

Term Definition
Geo The product name given to the feature that provides the ability to create one or more read-only mirrors for the main/primary instance
Primary The main, primary instance where read-write operations are allowed
Secondary An instance that synchronizes with the Primary node where only read-only operations are permitted

Planning and Process

Our planning and build process is recorded on the planning page.

Demos

The demos are recorded and should be stored in Google Drive under "GitLab Videos –> Geo Demos". If you recorded the demo, please make sure the recording ends up in that folder.

Research Items

  1. Next Gen Geo