Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #4350

Closed
Open
Created 12 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Restore not restoring anything on new install

Closed

Restore not restoring anything on new install

Created by: jacob-swanson

I was using 5-0-stable up and running on one PC. I setup another PC with 5-2-stable with then intention of migrating the 5-0-stable data to it. I upgraded 5-0-stable to 5-2-stable and created a backup. I then attempted to restore the backup to the newer PC, the output is below.

sh-4.2$ bundle exec rake gitlab:backup:restore RAILS_ENV=production
Unpacking backup ... done
Restoring database ...
pg_restore: too many command-line arguments (first is "/var/git/gitlab/tmp/backups/db/database.sql")
Try "pg_restore --help" for more information.
done
Restoring repositories ...
Put GitLab hooks in repositories dirs [DONE]
done
Restoring uploads ...
done
This will rebuild an authorized_keys file.
You will lose any data stored in /var/git/.ssh/authorized_keys.
Do you want to continue (yes/no)? yes

Deleting tmp directories ... done

No repositories, database entries, or authorized_keys are restored, but the backup archive looks like it was created properly on backup and extracted when the restore starts.

Linked issues
0


  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: bbodenmiller

    Duplicate of https://github.com/gitlabhq/gitlabhq/issues/4217.

    By Administrator on 2013-06-19T20:43:46 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: jacob-swanson

    I made the changes in that issue, but it did not change the fact that nothing was restored. It only got rid of the pg_restore error message when executing the restore command.

    By Administrator on 2013-06-19T20:57:07 (imported from GitLab project)

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
None
Assign to
Milestone
No milestone
None
None
Time tracking
No estimate or time spent
Due date
None
None
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
1
1 participant
user avatar
Reference: gpt/large_projects/gitlabhq1#4350

Menu

Projects Groups Snippets
Help