Skip to content
Snippets Groups Projects
Closed Geo: disaster recovery (single-secondary)
  • Geo: disaster recovery (single-secondary)

  • Closed Epic created by James Ramsay (ex-GitLab)

    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
    • git LFS
      • object storage gitlab-org/gitlab-ee#3944 (replicated externally)
      • local (disk, NFS etc)
    • wiki
    • database (issues, merge requests, snippets etc)
    • attachments (images on issues and merge requests)
      • object storage gitlab-org/gitlab-ee#3944 (replicated externally) - BLOCKED BY gitlab-org/gitlab-ee#4163
      • local (disk, NFS etc)
    • CI logs and artifacts
      • object storage gitlab-org/gitlab-ee#3944 (replicated externally)
      • local (disk, NFS etc) gitlab-org/gitlab-ee#2388
    • container registry

    The disaster recovery process should be simple and well documented, so that in the event of a disaster, the recovery process is quick and does not have the potential to make the situation worse.

    • Omnibus (one primary instance, one secondary instance): fail over to secondary, fail back to original state
    14 of 16 checklist items completed · Edited by James Ramsay (ex-GitLab)

    Linked items 0

  • Link items together to show that they're related or that one is blocking others.

    Activity

    • All activity
    • Comments only
    • History only
    • Newest first
    • Oldest first