search

christianspecht / scm-backup

Makes offline backups of your cloud hosted source code repositories
https://scm-backup.org/
GNU General Public License v3.0
61 stars 20 forks source link

Resuming interrupted backups #57

Open astatine- opened 4 years ago

astatine- commented 4 years ago

I have a bitbucket account with dozens of repos. While backing up, after about 25 odd repos, I saw this error (see below). Starting scmbackup again restarts from the first repo. Is there a way to make it skip the already downloaded ones? Perhaps the commit hash can be used to compare if it is already present? Any suggestions to resume interrupted backups will be very helpful. Thanks for your time and effort in creating and maintaining this.

fatal: protocol error: unexpected 'Error running git: fork/exec /usr/bin/git-upload-pack: no such file or directory'

Backup failed!
The application will close in 5 seconds!

-arun

christianspecht commented 4 years ago

SCM Backup only makes a full clone when it backups the repo for the first time. After that, it just does git fetch, i.e. it only checks if there are new commits in the repo on the server, and if yes, it only pulls those.

IMO, skipping some repos doesn't make sense, because for a full offline backup of your Bitbucket account, you want SCM Backup to pull every repo on every run.

It makes more sense to find out why it's failing.
SCM Backup doesn't do any special Git magic, it just calls the Git executable that's on your machine.
Your error message sounds more like a problem with your Git installation.

Do you have another machine where you can try it?

christianspecht commented 4 years ago

Interesting...now there are two more people who have the same issue.

Additional questions:

astatine- commented 4 years ago

I am a new SCM Backup user and the first time I tried it, it had failed on one of the repos. I manually fetched the repo which had failed and move on. In all 3 of my repos failed (and it is the same three that failed over multiple runs). I ran git manually and backed them up and added those 3 repos to the ignore list so that I can run SCM Backup without any errors subsequently. I had also tried ignoring all repos that would get backed up so that the erroneous one was the first and it still had the same problem.

I just repeated the steps and they went through smoothly. I tried running SCM Backup under "Git CMD" instead of just "CMD" as the paths or other config could possibly be different - but the same error again. See screenshots below - run one after the other. Unfortunately it is a private repo and you can't access it to reproduce the issue. But I will be happy to help troubleshoot.

On 15-07-2020 02:15, Christian Specht wrote:

Interesting...now there are two more people who have the same issue <#58>.

Additional questions:

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/christianspecht/scm-backup/issues/57#issuecomment-658403940, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQOMLC5EVDYY55Y3HPW3LLR3S7V7ANCNFSM4OOWLTNA.

christianspecht commented 4 years ago

Sorry for the long delay - so far, I have no clue what could cause the problem, so I was not sure which questions to ask you.

Some ideas:

  1. The Bitbucket account that you're backing up: user or team?
    I know it's somehow unified now with Bitbucket's move to workspaces, but was it a user or a team before?

  2. Are you using Git only or did you have Mercurial repos until Bitbucket dropped support at July 1st?
    If you had Mercurial repos, did you delete them and then created new Git repos under the same name/URL? (and are those the ones that are failing now?)

  3. I already asked you to try the steps SCM Backup does directly in Git, with the repo where the problem occured.
    Can you try this again, but this time from the directory where your local SCM Backup installation is?

  4. Under which operating system are you running SCM Backup?

PS: I don't see the screenshots that you mentioned in your last answer, do you still have them? If yes, please post here.