How good will an encrypted mount in Windows work for BackBlaze's Unlimited backup using their Windows application?

What is the problem you are having with rclone?

BackBlaze has an unlimited backup for $7 bux. To use it, you have to use their Windows software.

I want to encrypt everything before their program picks it up for backup.

I don't have enough storage to keep two copies of all my data: the actual data and the encrypted copy that the Windows program would pick up for backing up.

So my thought is to created an encrypted mount in Windows that points to my data and then have the BackBlaze windows app pick it up.

I'm wondering how well this may or may not work?

I am aware of BackBlaze B2 and was using it for a while but if I can get my above idea to work then it'll save me a lot of money.

Run the command 'rclone version' and share the full output of the command.

N/A. I have not installed rclone yet.

Which cloud storage system are you using? (eg Google Drive)

BackBlaze (not B2)

The command you were trying to run (eg rclone copy /tmp remote:tmp)

N/A

The rclone config contents with secrets removed.

N/A

A log from the command with the -vv flag

N/A

how much data do you plan to backup?

fwiw,
assuming that it could even work, too fragile to trust for backups and disaster recovery.

Initial set is 1.4 TB. Then maybe MB worth of changes a day.

so you want to double encrypt your data?

  1. rclone crypt
  2. B2 software

in my case,
for recent backps -> wasabi
for older backups -> aws s3 deep glacier at $1/TiB/month

I don't trust Backblaze encryption (I don't trust anyone's encryption) and I will disable it in BB if possible.

yeah, i get what you mean.
however, a bit confused, as you want to depend on rclone encryption.

so is the issue client-side encryption versus server-side encryption,
that only you have the decryption key?

rclone crypt is rock stable, never seen a single bug or issue in the forum,
on the other hand, rclone crypt has never been audited by a third party.

True. I wonder if BackBlaze's has been audited.

I have looked through rclone's code which gives me some comfort.

S3 remotes have client-side encryption, SSE-C
and the encryption is done by the aws go library, not rclone.

that is one of the many reasons, i only use S3 for backups.