Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • infrastructure infrastructure
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 107
    • Issues 107
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch Linux
  • infrastructureinfrastructure
  • Issues
  • #200
Closed
Open
Created Oct 25, 2020 by Sven-Hendrik Haase@svenstaroDeveloper

GitLab backups sometimes fail with file changed as we read it

GitLab backups sometimes fail if some files change while it's streaming.

The documented way to guard against exactly these kinds of issues is to use STRATEGY=copy as per https://docs.gitlab.com/ee/raketasks/backup_restore.html#backup-strategy-option. It does take 1x more disk space as there'll be a copy made before tarring stuff up but that's well worth it if it means we'll get more reliable backups.

See also https://gitlab.com/gitlab-org/gitlab/-/issues/7314

Edited Oct 25, 2020 by Sven-Hendrik Haase
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking