Disaster Recovery Practice (DR Gamedays)
Purpose
There are many reasons to test and practice our disaster recovery process for GitLab.com.
- Ensure our processes work as expected.
- Keep up with changes that could break or complicate our recovery processes.
- Increase confidence and knowledge of these processes for those who participate in the on-call rotation.
- Satisfy compliance requirements around validation of disaster recovery scenarios.
Overview
These practices are often referred to as DR gamedays
or just gamedays
.
Currently, our DR gamedays focus on zonal recovery scenarios, and each one focuses on a specific component.
During a real zonal failure, these gamedays should be capable of being executed in parallel to save time.
graph TD A(Assign Gameday) --> B(Perform Gameday) B --> C{Were there problems?} C --> |Yes| D(Document problems in the<br>Production Engineering Issue) C --> |No| E(Record Gameday Measurements) D --> E E --> F(Update Confidence Levels)
Gameday Assignment
Each quarter, eachPhase 1
component gameday process is assigned to a participating team.
This allocation should help us test each process once a quarter.
- The Ops team will create issues in the Production Engineering issue tracker.
- This issue is assigned to the next team in order to perform the practice.
Performing the Gameday
- Create a gameday change issue using the appropriate template.
- Review the process and consult the Ops team if any part of the process is unclear.
- Schedule the gameday, seeking out proper review and approvals for the change.
- Execute the gameday. It is recommended to work with a reviewer during the process to record problems, timing, and approving merge requests during the process.
Reporting Gameday Process Issues
Compile any feedback from the gameday and update the Production Engineering issue. The Ops team member who created the issues will be the directly responsible individual tasked with incorporating the feedback into future practices.
Recording Gameday Results
Open merge requests to update the timing and execution information from the gameday.
Updating Confidence Levels
As services change, and processes are improved, the ops team is tasked with managing the confidence level measurements.
fb665961
)