Customer want a disaster recovery solution to prevent their organization being severely impacted by a data center outage or some other major failure. We also want to be able to use such a solution for GitLab.com.
A key component of disaster recovery is making sure that data is replicated and current in another location that is accessible. GitLab Geo provides this foundation.
To offer a comprehensive disaster recover solution, everything needs to replicated and accessible:
- git 10.2
- git LFS
- wiki 10.2
- database (issues, merge requests, snippets etc) 10.2
- attachments (images on issues and merge requests)
- CI logs and artifacts
GitLab Pages assets (
.jsetc that will be served)
- ElasticSearch #1186
We want to offer a Disaster Recovery solution that our customers will want to buy, but also that we will be able to use it ourself for GitLab.com. GitLab.com is the biggest GitLab installation that we know of, and has its own constraints. However, we are confident that if we fix this issue for us, it will be beneficial for our customers, and we will be alerted of the potential bugs before our customers, making it a more solid product.
The feature will be called Disaster Recovery, once marketed.
- Basic manual failover from primary to secondary (incl HA installations) #1921 10.3
- Verify uploaded files gitlab-ce#39949 10.4
- Verify repositories #4057 (closed) 10.4
- Planned failover process migrating between data centers (like the GCP migration)
- Support Elasticsearch in Geo secondary nodes #1186