Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • reliability reliability
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,809
    • Issues 1,809
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.com
  • GitLab Infrastructure Team
  • reliabilityreliability
  • Issues
  • #1102
Closed
Open
Created Feb 01, 2017 by Yorick Peterse@yorickpeterseContributor

Automated testing of recovering PostgreSQL database backups

We need a procedure to recover a PostgreSQL backup. This could be something along the lines of the following:

Once a week a host is started automatically, or otherwise woken up somehow. Once it starts it will try to grab the most recent database backup and use this to start a local PostgreSQL database. Once this process has completed it will connect to the DB and check a few tables to see if there's data (e.g. users, projects, and issues). If these tables don't have any data, or the restoring process failed, errors should be sent to Slack.

This restore procedure should use the same underlying tools as a production engineer might use to manually restore a backup. This means we can automatically (and periodically) test these tools, removing the need for engineers to do this manually.

Assignee
Assign to
Time tracking