## Short description <!-- add a short summary of what is being proposed --> The container registry meta db is not currently being considered for backup using the current backup and restore rake tasks https://gitlab.com/gitlab-org/gitlab/-/issues/532507 This feature is [committed to be GA by Q4](https://gitlab.com/gitlab-org/gitlab/-/issues/532507#note_2511480980) so we need to create a backup and restore solution for customers. ## Connection to technical roadmap <!-- Link to https://infra-roadmap-c6d14f.gitlab.io/ items, such as https://infra-roadmap-c6d14f.gitlab.io/#project-durability_unified_backup_restore In the technical roadmap [YAML](https://gitlab.com/gitlab-com/gl-infra/infra-roadmap/-/blob/main/data/stage-data_access.yml), explain how the project aligns with stated goals of the company. Which goal(s) is it helping along? - [FY26-28 Platforms strategy](https://docs.google.com/document/d/1E5T9TSkqxWkvCpWNbfrqmEFM5sXMO4HT-D22m_QjfyA/edit?tab=t.0) - [FY26 Data Access Product Outcomes](https://docs.google.com/document/d/1ymSJU24RkSC7n4YzuwYgQj6F8Yx_rNsSBk-2hIgkxI4/edit?tab=t.0#heading=h.lun6ty6cqwk6) - [FY26 plan from Bill](https://university.gitlab.com/learn/course/draft-fy26-company-memo/main/fy26-company-memo?client=internal-team-members&page=3) - [Data Access Vision](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/data-access/#vision) Don't forget to link back this epic from the yml. --> ## Expected impact <!-- What will happen? How will it be measured? --> - Meet customer requirements for backup and restore that includes the Registry meta db. ## Exit criteria <!-- When is it done? Prevent scope creep by defining it here! --> 1. We can backup and restore the container registry db in both Omnibus and CNG environments 1. Registry meta-database is part of our automated backup and restore testing ## Timeline and Effort <!-- How much time do we think it'll take to complete? Wild guesses are appropriate here! We can always iterate on any section here. --> <!-- DO NOT EDIT BELOW - Used for the epic status automation bot --> <!-- STATUS NOTE START --> ## Status 2026-02-26 This week saw active development across multiple implementation tracks for the Container Registry database backup feature. The Omnibus backup role MR ([omnibus-gitlab!9129](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/9129)) received significant attention with architectural discussions around making the role additive and organizingation of the omnibus-gitlab changes. :clock1: **total hours spent this week by all contributors**: 8 :tada: **achievements**: - [charts/gitlab!4717](https://gitlab.com/gitlab-org/charts/gitlab/-/merge_requests/4717) — Changes for Cloud Native GitLab are progressing through maintainer review - [omnibus-gitlab!9129](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/9129) — Draft MR implementing the Omnibus backup role received substantial review activity: - Architectural discussion resolved: the backup role will be **additive** (not disabling other services), making it safe for single-node deployments. - Core Rails change [gitlab!215296](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/215296) continues progressing through review :issue-blocked: **blockers**: - [omnibus-gitlab!9005](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/9005) — Still awaiting **maintainer review**. This is the primary blocker for the Omnibus track; it implements registry backup credentials and must merge before [omnibus-gitlab!9129](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/9129) can follow - The core Rails change [gitlab!215296](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/215296) not yet being merged makes end-to-end testing in downstream MRs more difficult :arrow_forward: **next**: - Obtain review and merge [omnibus-gitlab!9005](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/9005) - Continue refinement and review of the backup role in [omnibus-gitlab!9129](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/9129) - Merge [charts/gitlab!4717](https://gitlab.com/gitlab-org/charts/gitlab/-/merge_requests/4717) once maintainer review is complete - Complete backend and database review on [gitlab!215296](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/215296) - Begin documentation work per [gitlab#581281](https://gitlab.com/gitlab-org/gitlab/-/issues/581281) and plan integration testing once primary MRs are merged _Copied from https://gitlab.com/groups/gitlab-com/gl-infra/data-access/durability/-/epics/45#note_3114193084_ <!-- STATUS NOTE END -->