Latest Blog Posts
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.
Cloudback sends an email notification to the user if the backup fails. By default, we are using the primary email address taken from the GitHub profile.
We received a feature request to support custom emails for notifications. This may be useful when you have a separate email for such kinds of notifications. We decided to provide such functionality for every account where the Cloudback GitHub Application is installed. Now you can set up a new email address for failed backup notifications for each account using the Account Settings dialog:
Cloudback provides an easy way to store GitHub repository backups in various storages. And today, we are delighted to announce the support of new storage - Microsoft OneDrive.
We received a request to support this storage via email, but to make our work more transparent, we created a related issue in our public issue tracker. The development process from the initial request to a production-ready solution took about a month, including two weeks of waiting for the verification from the Microsoft side.
A few weeks ago, we got a new feature request in our issue tracker. One of Cloudback users asked us to add support for the OpenStack Swift storage provider. We discussed the feature request within the team and started development. We decided to use an S3 API gateway of OpenStack Swift. As a side effect, we introduced an S3 access-key-based provider in addition to OpenStack Swift. Now Cloudback supports any S3 API compatible storage provider.