Incremental Encryption Backblaze

Z3120 shared this idea ago

Under Consideration

It would be great to see encryption for Backblaze's B2 Incremental destination / backup type implemented.

https://github.com/Backblaze-B2-Samples/encryption

I like this idea

Replies (2)

JetApps Requests Admin ●

Hello,

Thank you for submitting your feedback! We will be reviewing it and update accordingly! Please note that our team uses the voting feature to gauge demand for all feature requests. The more votes a request has, the more likely it will be up for consideration from our developers. Please keep an eye on this request and our social media for any updates regarding Incremental Encrypted Backups to BackBlaze.

Thank you again for your support of our product!

Best Regards,

JetApps Team

Reply URL

Mnswj ●

This should be a very easy implementation for JetApps to do now that BackBlaze has implemented SSE-C on their side. You would simply need to include an additional header during each upload and download with the encryption key, and BackBlaze does all of the work!

Reply URL

JetApps Requests Admin ●

Hello,

Thank you for your interest in this feature request and for providing additional feedback. Just to clarify, in JetBackup 5, the Backblaze destination type is now a part of the S3 Compatible Plugin which supports all S3 Compatible vendors such as Backblaze, Wasabi, Google Cloud Storage, and more. Because JetBackup 5 now uses the S3 Compatible plugin, our developers are unable to apply custom headers to the requests being made to Backblaze Destinations and instead need to use a method that ALL S3 Compatible Vendors will support.

With this being the case, our developers are still evaluating the possibility of having Encrypted Incremental Backups to S3 Compatible Destinations and will provide additional updates as soon as they can.

Best regards,

JetApps Team

URL

Mnswj ●

The header I mention is not specific to backblaze. It is a standard S3 header. Other S3 destinations that support encryption would use that same header as well.

URL