• You can now download the full repository including all branches directly from BackHub.

    Until now it was only possible to download a checkout of the latest commit in your master branch as a zip file. However, many users found it irritating that the download contains only files from one branch and thought the backup was incomplete.

    That’s why we have changed things and it is now possible to download the complete repository directly from BackHub. That comes in handy if you don’t want to restore the complete repository back to GitHub but still want to work with the repository on your local machine or transfer it to another service.

    Another minor thing we’ve changed is the filename of the downloaded zip file. It’s now using the repository’s name as a filename.

    In future we are planning to support cloning directly from BackHub servers via https.

  • While building and running BackHub the last three years, we got lots of user feedback and learned a lot about how a backup solution for GitHub should be like.

    One major concern of larger organizations is often to hand over their most valuable data to a young and small startup in a foreign country for the purpose of creating backups.

    A distributed version of BackHub that is being run on site behind the firewall could solve this issue but would have many drawbacks in terms of maintainability and convenience.

    We’ve decided to go with a solution that lets you use your own, separate storage account with an independent third party company (Amazon S3) to keep all the convenience of a service that is run in the cloud while keeping full control of their data. Another big advantage of this solution is that your data can be accessed anytime, even if GitHub AND BackHub is unavailable.

    For BackHub Enterprise we’ve also developed a new way to store backups incrementally. That means you can restore a repository from the last 30 days.

    If you are interested in using BackHub Enterprise for your organization, please leave your email address and we will notify you when it’s available.

  • We’ve been running and improving BackHub since 2014 as part of our web development agency /gebrüderheitz GmbH & Co. KG. We’ve been growing and learning ever since and are now moving things over to a separate business entity, the so called “BackHub UG”, based in Berlin, Germany. From now on, BackHub.co is being run by BackHub UG (limited liability).

    Therefore we’re updating our terms of service and privacy policy. If you’d like to read our updated terms, you can do so here. Everything else stays the same, same conditions, same team, same service.

    There’s no need to respond to this email, by continuing to use BackHub, you agree to these updated terms of service and the privacy policy.

    Happy New Year everyone.

    The BackHub Team

  • We have renamed a couple of things in the list of repository backups and introduced a new differentiation between archived backups with upstream to the original repository at GitHub and archived backups without upstream.

    Let me explain in detail what these different states mean and how they look like:

    Repositories without Backups

    GitHub Repositories without Backups

    This section contains all repositories you have at GitHub that do not have any backups. Depending on whether you have automatic backups activated or not, you will either see “Backup scheduled” or a button “Backup”. “Backup scheduled” means automatic backups has just been activated, but backups are not yet created. This usually happens between 2:00 – 6:00 am CET.


    Backup GitHub Repositories once a Day

    This section contains all repositories with active recurring backups. “active recurring” means we are updating the backup for this repository once a day between 2:00 – 6:00 am CET.


    Archive GitHub Repositories

    This section contains all repositories with backups that have been archived. Archiving means, the backup is not being updated on a daily basis. On the right side of each repository you will find the information, when the last backup has been made.

    Now there are two different cases for archived backups. Firstly, a backup for a repository that is still existing at GitHub and secondly, a backup for a repository that has been removed from GitHub. When a repository at GitHub with an active backup at BackHub is being deleted at GitHub, BackHub automatically archives the backups since the upstream is no longer available.

    Archived Backups with upstream to the original repository at GitHub

    ...with upstream to the original repository at GitHub Backups with upstream to the original repository at GitHub do have a solid border and a link to the repository at GitHub as well as an option to reactivate recurring backups.

    Archived Backups without upstream to the original repository at GitHub

    ...without upstream to the original repository at GitHub Backups without upstream to the original repository at GitHub do have a dashed border without link to GitHub since the original repository is no longer available.

  • In addition to “Download Metadata” which let’s you download all metadata of your repository backup like Issues, milestones and more, you can now also download the files of a GitHub repository backup as a ZIP archive.

    The archive contains a checkout of all files from the head of your default branch in your GitHub repository. It’s much like the “Download ZIP” Button you know from GitHub.

    This is especially handy if you want to quickly have a look into your files without having to restore the whole repository back to GitHub.

    Download the Files of a GitHub Repository as a ZIP Archive

    The next milestone for downloading backups is to let you clone the complete repository so you can access your repository at any time without having to restore it back to GitHub.