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 …
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 , 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 . 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 …
You may have noticed the gift icon in the main menu!
It’s a little gift from us to express our gratitude for recommending BackHub to your friends and followers who sign up and start using BackHub.
Increasing our user base gives us more resources to build new features for you.
The great thing is, you can give the same gift to your friends as well, because they will also receive 10 forever free repository backups on their account if they use your referral link.
To recommend BackHub to your friends, click on the little gift icon in the main menu and you will find your referral link.Read more …
You can now clone any of your GitHub repository backups directly from the BackHub servers. You can also clone any of the snapshots available for a specific backup. In BackHub, open the panel of the backup you want to clone, select the snapshot in the footer of the panel, and copy the clone URL.
For this feature to work, there must be an SSH key stored in your GitHub account. We fetch this key to authenticate the client when cloning. For new users, this feature is enabled by default. For existing users, enable it in the user settings.
Note:This feature is part of our effort towards enabling you to access your GitHub backup even when GitHub is temporarily unavailable. We recommend noting down the clone URL so you can clone without relying on the web frontend.Read more …
In June 2018 many of us were surprised to see Microsoft announce the purchase of the developer platform GitHub for $7.5 billion. GitHub confirmed the deal . Wow! What a bomb. This is only the tenth multi-billion dollar acquisition of Microsoft in its history.
As developers and frequent users of this platform, quite a few important questions instantly popped up. Specifically, we started asking: