Why doesn’t SCM Backup support backing up local installations of [hoster X]?

SCM Backup only supports backing up from the hosters’ cloud offerings. Most hosters also support some kind of “install on your own server” version of their product, but SCM Backup doesn’t support any of them, and this is very unlikely to change.

The main reason is: Supporting local installations would make automated testing much more complicated.

SCM Backup has a load of integration tests which are executed for each supported hoster, calling the hoster’s API and actually backing up test repositories - all by just using the hoster’s existing cloud infrastructure.

For “install on your own server” versions, setting this up would be much more complicated: For each hoster, we’d need a local installation running somewhere…and reachable from the internet, so our CI provider (currently AppVeyor) can access it.

And not all hosters even offer a free-as-in-beer version of their local product - for example, the only version of Bitbucket Server that’s freely available seems to be a 30 day test version.


If you are using a local installation of a hoster supported by SCM Backup (or any other Git/Mercurial/whatever server that can be installed on a machine you control), you probably don’t need a tool like SCM Backup!

You (or at least someone in your organization) should have enough access to the machine, so you can directly backup the folder from that machine which contains all the repositories.

Why do the docs mention Mercurial, but none of the supported hosters supports Mercurial repos?

Bitbucket did support Mercurial, until they dropped support for it and deleted all repos in July 2020.

Until then, SCM Backup was able to backup Git and Mercurial repos from Bitbucket.

Support for Mercurial (and all references to it in the documentation) will not be completely removed from SCM Backup, so we’ll be able to support backing up from Mercurial hosters in the future.