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

Category Strategy - Disaster recovery

🚨 Disaster recovery

   
Stage Enablement
Maturity minimal

Introduction and how you can help

GitLab installations hold business critical information and data. The Disaster Recovery(DR) category helps our customers fullfill their business continuity plans by creating processes that allow the recovery of GitLab following a natural or human-created disastery. Disaster recovery complements GitLab's High Availability configuration and utilizes Geo nodes to enable a failover in a disaster situation. We want disaster recovery to be robust and easy to use for systems administrators - especially in a potentially stressful recovery situation.

⚠️ Currently, there are some limitations of what data is replicated. Please make sure to check the documentation!

Please reach out to Fabian Zimmer, Product Manager for the Geo group (Email) if you'd like to provide feedback or ask any questions related to this product category.

This strategy is a work in progress, and everyone can contribute:

🔭 Where we are Headed

Setting up a disaster recovery solution for GitLab requires significant investment and is cumbersome in more complex setups, such as high availability configurations. Geo doesn't replicate all parts of GitLab yet, which means that users need to be aware of what they can recover in case of disaster.

In the future, our users should be able to use a GitLab Disaster Recovery solution that fits within their business continuity plan. Users should be able to choose which Recovery Time Objective (RTO) and Recovery Point Objective (RPO) are acceptable to them and GitLab's DR solutions should provide configurations that fit those requirements.

A systems administrator should be able to confidently setup a DR solution even when the setup is complex, as is the case for high availability. In case of an actual disaster, a systems administrator should be able to follow a simple and clear set of instructions that allows them to recover a working GitLab installation. In order to ensure that DR works, frequent failovers should be tested.

🎭 Target Audience and Experience

Sidney (Systems Administrator) - Persona Description

For more information on how we use personas and roles at GitLab, please click here.

🚀 What's Next & Why

What is Not Planned Right Now

The GitLab DR category is not a replacement for off-site backups and we currently do not plan to include any additional backup methods into our disaster recovery category.

Maturity Plan

This category is currently at the minimal maturity level, and our next maturity target is viable (see our definitions of maturity levels).

In order to move this category from minimal to viable, one of the main initiatives is to create a simplified disaster recovery process. High Availability configurations are also fully supported and all data is replicated.

🏅 Competitive landscape

We have to understand the current DR landscape better and we are actively engaging in customer meetings to understand what features are required to move DR forward.

Analyst landscape

We do need to interact more closely with analysts to understand the landscape better.

Top Customer Success/Sales issue(s)

🎢 Top user issues

🦊 Top internal customer issues/epics

Top Strategy Item(s)