3 ms·
Thanks for the feedback. 1. Yes, you have to restore a backup on exactly the same version of GitLab and then upgrade that version. If you restore it to a diffe
by sytse 8y ago
Thanks for the feedback.
1. Yes, you have to restore a backup on exactly the same version of GitLab and then upgrade that version. If you restore it to a different version the database scheme isn't correct.
2. You can restore a GitLab backup anywhere https://docs.gitlab.com/ee/raketasks/backup_restore.html https://docs.gitlab.com/ee/raketasks/backup_restore.html as long as it is the same version. I think the output is a single file.
- Aeolun 8y agoThanks for the response. 1. Gitlab is able to migrate up to a new version, so is there anything preventing it from getting up to a certain (older) version before running the last few migrations after restore? If I set up a new instance it’s generally one or two minor versions higher than the old instance. 2. I swear I restored from my omnibus installation to Helm based gitlab and lose all my uploads and registry images. Cannot see from the docs why that would happen any more though. Maybe it was the opposite, with me restoring the backup to the same block storage devices, and gitlab hiccuping on the fact that all the files it wanted to restore were already there.
- sytse 8y ago1. I'm not sure and will ask. 2. It might be that this wasn't supported yet in the Helm chart at that time, I'm not sure.
- twk3 8y agoWe've opened https://gitlab.com/charts/gitlab/issues/1015 https://gitlab.com/charts/gitlab/issues/1015 to discuss this comment. I don't believe the db migrations are what are holding us back, as much as the other parts of the backup/restore. For number 2, that sounds unexpected, and we would love for you to give us more details. https://gitlab.com/charts/gitlab/issues https://gitlab.com/charts/gitlab/issues