Latest Blog Posts
Cloudback provides an easy way to store GitHub repository backups in various storages. And today, we are delighted to announce the support of a new storage - Wasabi Cloud Storage.
Wasabi provides simple, predictable and affordable hot cloud storage for businesses all over the world. It enables organizations to store and instantly access an infinite amount of data at 1/5th the price of the competition with no complex tiers or unpredictable egress fees.
The Cloudback team is happy to announce that an alternative view for Cloudback Dashboard is released. It is a Table View. Using table view it is much easier to navigate through a large number of repositories and trigger on-demand backups. We put the Table View Toggle in the header, so it is always easy to switch to the Table View and back to the Card View. It was a feature request of our client and we are glad to deliver it.
Four months ago, in February 2022, we received a new feature request from our user in our issue tracker. In the request, the user asked us to implement real-time notification support via messengers. As soon as a backup fails or succeeds, he should receive a notification. We found the request extremely useful and prioritized it in the backlog of our project. Despite the delay in delivery, we are happy to say that the work is done and the feature is now available.
The Cloudback team is pleased to announce a new feature: Data deduplication for custom storage. The use case is a daily backup for a GitHub repository that’s not changed every day. The feature prevents wasting storage space just because Cloudback saves backup archives with the same content every day, even though nothing has changed in your GitHub repository. In certain scenarios, the feature can drastically reduce storage costs.
The configuration of all existing custom storages remains unchanged and data deduplication is disabled.
For security reasons, Cloudback uses AES-256 encryption for all backup archives. If you download a specific backup, you can access its content using the password. The password is sent automatically to your GitHub account primary email. However, some people may find this approach a little bit overcomplicated, especially when using custom storage somewhere inside your own secure infrastructure.
We are glad to announce that it is possible to opt-out of password-based encryption now.