Thanks Nigel. I am passing the buck regards not having a previous backup. It was the first thing I planned on doing until I discovered that the server was broken.. (the guy who set up the gitlab neglected to set up any backups)
I have cloned the server hard drive - before fiddling :) I now have all the repos on USB with passkeys (gitlab-secrets.json) Re-importing them seems to be the option I have to take. The documentation seems a little lacking, but I will try to google my way through. Expect more confused posts to follow! Thanks Paul On Friday, 1 July 2016 12:21:22 UTC+1, Nigel Metheringham wrote: > > I would suggest:- > > - copy off all the git repos - make sure they are out of harms way > - going back to your most recent gitlab backup (you may need to build > a server with matching gitlab version) > - upgrade to current > - work through all the repos pushing the contents to the new gitlab > instance > - you may have lost some recent updates outside of the git repos > > If you do not have a gitlab backup then that is probably a warning in > itself. > > In that case reimporting all the repos anew is the best you can do most > likely. > > In any case make sure you save the state of the damaged system somewhere > offline (different server, USB disk etc) before fiddling. > > Everyone else: check your backups. Ask what your disaster recovery plan > is for something that is likely to be a core part of your team's value. > > Nigel. > > Paul Claydon <javascript:> > 1 July 2016 at 11:45 > Hi > I have a local pc serving the gitlab. Somehow the thing is broken. (its > long story, but if anyone really wants to know I can try to explain) > > So I can boot to a shell prompt. When I try to rake a backup the cursor > just sits there flashing, no output. > > Is there any way to just copy all the repositories and the passkeys and > start on a fresh gitlab server? > > (currently I'm trying to copy the git-data folder to a usb, and all the > /hooks are not copying - cannot create symbolic link) > > Any help/pointers would be appreciated > > Thanks > Paul > -- > You received this message because you are subscribed to the Google Groups > "GitLab" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to gitlabhq+u...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/b03160aa-71e4-408f-919a-a981cd16b8d3%40googlegroups.com > > <https://groups.google.com/d/msgid/gitlabhq/b03160aa-71e4-408f-919a-a981cd16b8d3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > > [ Nigel Metheringham ------------------------------ ni...@dotdot.it > <javascript:> ] > [ Ellipsis Intangible Technologies ] > > > > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/49d18ad1-3232-4dfd-b9ce-fe7b70215c10%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
