Worth noting on this that while sync works, copy is the much safer option.

So

rclone copy source:/path dest:/path is what I'll likely end up using. In any case, the resulting solution still works.

Still need to tweak OSX a bit as it seems to kill the SSH session after some time for sporadic reasons - still testing but I may end up having to add ServerAliveInterval 120 to /etc/ssh/ssh_config to resolve that issue.

@DustinB3403 said in Syncing massive amounts of changing data to BackBlaze B2 via Linux:

@Pete-S At my workstation I'm getting 225Mbit/s down and 155Mbit/s up (clearly not symmetrical there. . .) but not bad either considering I have nothing special configured for my workstation.

On a second test I noticed this A connection of 152.8 Mbps upload would backup 1,650 GB in a day

So this very well could be feasible to do.

Yes, that's not too bad. It could work. As @dafyre and other mentioned you should give it a try.
$.005 per GB is $5 per TB. So get an account and upload 2TB of random data to see how long it takes. Only going to cost you 10 bucks to find out.

@dafyre said in Its is okay to sync/delete often from Cloud Storage?:

@scottalanmiller said in Its is okay to sync/delete often from Cloud Storage?:

I don't believe that there is any charge for Wasabi deletions.

From what I can tell, Wasabi only charges for storage. There are no egress or deletion fees.

Correct, same here. Unless you have the old accounts where they did charge for egress.

Got it. I was using the account id with an application key.

A more careful reading of the above linked page shows that:

0_1542076748186_e6061550-5167-4def-b9b5-5b89e859f408-image.png

So that was the disconnect.

Application Key requires Application ID. Account ID requires Master Application Key.

When the examples clearly stated ACCOUNT_ID and APPLICATION_KEY

0_1542076683650_e8a7c2f9-0a93-4c35-b429-0bf24767fe33-image.png