Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • G git-backup
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • git-backup
  • Issues
  • #7

Closed
Open
Created Jan 27, 2017 by iv@iv

Remove by hand files that were left by previous run

I just wanted to document this issue for new gitlab-backup users:

When gitlab-backup restore -vupok -go SHA1 has been interrupted, the error message shows up when running again:

E: /srv/slapgrid/slappart6/srv/runner/instance/slappart0/var/backup/abignumberhere_gitlab_backup.tar already exists

Solution: Remove that old file.

Re-running may give another error:

cmd_restore: mkdir /srv/slapgrid/slappart6/srv/runner/instance/slappart0/var/repositories.abignumberhere: file exists

Solution: Remove the tar container (which was re-created) + this folder.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7