GitLab's 2017 Backup Failures Show Why Nightly Restore Tests Matter

In January 2017, a GitLab.com engineer accidentally deleted a PostgreSQL data directory on the primary server, causing an outage of about 18 hours. The team discovered that none of its five backup and replication methods worked reliably, including a pg_dump job that silently produced near-empty files due to a client-server version mismatch. Roughly six hours of database changes were lost, and data was eventually recovered from a staging copy taken for load testing. GitLab's postmortem blamed the incident on no one being responsible for testing the restore procedure. The article proposes a nightly script that dumps, uploads, downloads, and restores the backup into a scratch container, comparing row counts before signaling success.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in