Originally posted by BruceBanner ...
Backblaze sounds similar, may I ask you fine gents what kind of upload speeds you experience? I'm only getting about 5mb/s, and this is on data plans where I am not on unlimited (no NBN yet).
I like the idea of backing up more than just the RAW files and LR catalogs from a job, such as some personal (non image) files as well as perhaps more RAWs of the same job but that were initially culled and never made it into LR's library etc. But I fear my data plan and upload speeds must be taken into account, I doubt I can cope with a service like Crashplan or Backblaze currently.
I never thought about speed, but just tried a run and I get 10-15 mbyte/s upload (~100 mbit), and I'm in Sweden while their servers are in the US as I understand it, but I think that may be my ISP upload limit so perhaps not a backblaze limit. But since that just uses some disk and network and no cpu and could basically be "always on" if you wanted to, even while editing photos without interfering much with performance since it doesn't use a lot CPU, GPU or RAM, so I don't think the upload speed should be an issue anyhow?
Regarding what to backup, as I mentioned, with the commandline tool and b2 storage (and not the "whole computer backup"-plan) you can easily specify what to backup and not to further limit whats uploaded. The computer-backup has some build-in restrictions on temporary files, application files etc, so you can't restore a computer installation with OS and all from it, just the data. In my case I just run
b2 sync --dryRun --compareThreshold 1 [path to my photo storage]
to sync see what will be uploaded from the photo raw drive, no actual transfer, and then
b2 sync --compareThreshold 1 [path to my photo storage]
to actually to the sync, but there are many options and details that allow for customization and you can run this on a schedule in windows or linux at least (probably in macos too). The comparethreshold-part is just because linux uses different precision of file datetimes compared to windows, and I use both, so maybe not necessary in your case.
As for security as someone mentioned, you can either encrypt it yourself before uploading, or they also have support for you to provide/configure your own encryption key locally so that Backblaze themselves can't decrypt your data even if CIA tried to force them =).
Edit: About uploads/plan; since you define what to upload or not with b2, and it's all "syncing" and not uploading all the data every time, I don't see how you can get a full cloud backup using any less data no matter what solution you use? (Sure the whole-computer-plan from backblaze will backup more, but no need to use that). Or what you could do if willing to spend the time and effort you could try to compress raws using 7zip or so before uploading, but that won't gain much when dealing with raw files and also not worth it I think, since youre not doing that today? (nobody is probably..). But all in all, even if you just get 0.5 MB/s, leaving the computer on overnight would solve that, so the upload speed shouldn't be an issue regardless of plan I think. (if there's a cap on total upload in the plabn there might be issues, but that would go for any cloud backup regardless, and be more related to what you upload rather than to which cloud...)
Last edited by Igor123; 06-03-2019 at 02:49 PM.