Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
raketask gitlab:backup:restore aborts #1042
This appears it may be an Upstream issue but I wanted to post here to see if anyone has had the problem and overcome it in some way.
Current Instance and New Instance are running 8.15.2
rsync backup to new server, chmod 0644 file.
When I execute the docker to run the restore raketask the first sign of an issue is the "date: invalid date"
I can choose the backup file, the task starts but aborts at ** Execute gitlab:backup:restore
Thanks in Advance!
date: invalid date '@1483543531_2017_01_04'
Select a backup to restore:
Select a backup to restore: 1483533029_2017_01_04_gitlab_backup.tar
Tasks: TOP => gitlab:backup:restore
I was able to Workaround this issue by running the raketask through docker exec
I had to remove all but one backup as I did not try to feed the backup directly to the rake command.
I will play around with it a bit before I put this instance into production.
The relevant issue in GitLab issue tracker is https://gitlab.com/gitlab-org/gitlab-ce/issues/26090. It will be fixed by https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8477 and released in a patch release to 8.15.
As a heads up to the maintainers of this project: we changed the timestamp format from
So copy the EPOCH from your file and check the date with
Rename your file like @adamniedzielski said so in this case it would be
Now you can exec the command as follow:
Restoring from backup,I encounter a similar error,running
the trace info below:
This works for me (8.15.4) - It looks like the BACKUP needs a full file name, not just timestamp:
I tested in another environment and followed the original procedure of sameersbn/docker-gitlab found here and it worked (providing I kept the same database version).
The thing I wasn't doing correctly was creating the backup with the rake task with the NEW gitlab image. I was trying to restore a backup created with the old image into the new one, which failed.
As Gitlab docs specify : "You can only restore a backup to exactly the same version of GitLab on which it was created. The best way to migrate your repositories from one server to another is through backup restore" source