Start Free trial

Why do I need a GitHub repository backup?

To prevent loss of data

There are many reasons for keeping an extra offsite backup of your GitHub repositories.

The number one cause of data loss is directly from users.

Here are a few scenarios that can lead to loss of data in a GitHub repository:

  • A repository has been deleted accidentally from GitHub.
  • A repositories content has been wiped.
  • The history of a repository was changed with git-reset or git-rebase and therefore has led to loss of data with a forced push.
  • The contents of an issue or milestone etc. has been changed or deleted accidentally.
  • GitHub accidentally loses your data (happened to GitLab before).
  • Rogue employee destroys your data.
  • Your account get's hijacked (happened to the Canonical account).
  • Your account is deleted (GitHub deletes data immediately when the accuont is deleted).
  • Your account is blocked by GitHub.

There are many other scenarios that could potentially lead to loss of data. We therefore strongly recommend backing up all your data.

With BackHub you can restore your current backup directly back to GitHub or rollback to a previous state of your repository and metadata from any of the backup snapshots up to 30 days back in time.

For compliance

Many of our customers also need backups for compliance. If you are preparing for a SOC2 or ISO27K audit, for example, you will need a backup of your cloud data.

Read more in our help center.