To prevent loss of data
There are many reasons for keeping an extra offsite backup of your 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.
- 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
- Rogue employee destroys your data
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.
Many of our customers also need backups for compliance. If you are going through a SOC2 audit, for example, you will need a backup of your cloud data.
Why use a cloud to cloud backup service?
Outsourcing backup creation has the following benefits:
- No need to write your own backup script
- No need to ensure your backup script is up-to-date with GitHub API changes
- No need to monitor your own backup script
- No need to create your own documentation on backup and recovery procedures