• Today, we are releasing Cloud Sync, the most-requested feature to date. Cloud Sync is an option for automatically syncing your GitHub repository backups to your own Amazon S3 storage, with other cloud storage providers to be supported in future.

    Until now, backups have been stored on our data storage only, so customers lack direct access to them. Backups have only been accessible through the user interface for download, restore or by cloning from our server via SSH.

    Read more …
  • We’re excited about taking BackHub to the next level this year!

    We highly value customer feedback and also like to be transparent about our plans. These plans are based both on customer feedback and keeping up with evolving industry standards.

    In this post I’ll share our priority projects for 2019.

    Read more …
  • For all BackHub Basic customers we are replacing the BackHub OAuth App (BackHub Basic) with the new BackHub GitHub App (BackHub on GitHub Marketplace). If you are a BackHub Basic customer, it is required that you install the BackHub GitHub App to continue creating backups for your account.

    Read more …
  • At BackHub we recently celebrated our first year anniversary in the GitHub Marketplace.

    We’re very happy about our partnership in the GitHub Marketplace, and proud of how far we came in 2018.

    I’ll briefly share how we provided substantial value to customers during this productive and exciting year.

    Read more …
  • Why Consider Backup Strategies?

    Saving copies of your work as backups is essential to prevent data loss, especially in today’s digital and multi-connected world. The reasons range from hardware failures (manmade or natural) to accidental data deletion, damage or data loss due to a power outage, violence caused by burglars as well as encrypted data due to ransomware and stealing of hardware. An example for damages might be single bit changes on disk on older file systems without checksum (fat16, fat32 and ext2). Insurance policies require additional measures to ensure the safety of local and distributed work.

    While multiple storing data is relatively simple, backing up and restoring your data can be quite challenging. Take into account that backups can look good at first sight, but be unusable for a number of reasons, including that the full backup is corrupt because something in the I/O subsystem corrupted it, the storage media died, or even worse it is half-dead (partly readable). You might not have the hardware anymore to read the backups (e.g., floppy disk drive, tape reader or CD-ROM drive). Also, if a backup in the log backup chain is corrupt it means that restoring cannot continue past that point in the chain. Another situation is that sometimes data is simply forgotten so that the backup is incomplete. This leads to dramatic scenes, and according to Murphy’s law [1], it is the most important data that is not there. As always.

    This article will give you a short introduction into backups and the corresponding strategies [18]. Factors that are to be taken into account are storage space to keep the snapshots, speed for backup/restore and the possibility to trace the changes in your backup set.

    Read more …