Skip to content

GitLab

  • Menu
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
  • #2944

Closed
Open
Created Feb 08, 2013 by Administrator@rootOwner

Migrate from 3.1 to 4

Created by: ghost

Hi Gitlab team

I'm trying to migrate my gitlab 3.1 to the new gitlab 4. I do the steps to backup the sqlite3 database, i'm copying the data.yml file on the new server with the mysql, run the setup and when i'm trying to load the database, it starts, and stays on that state without changing.

I have used the --trace but nothing comes out. The data.yml is about 80MB. It never stops the load. The cpu stays at 100% for the ruby process and there are some requests to the mysql server, but i don't see anything in the tables.

Can anyone give me help on that issue? Have anyone see something like that? Thanks for your time

Assignee
Assign to
Time tracking