When you sell "Securely store all of your photos, videos, files and documents" in a world where drives holding multiple TB of files has been available for low prices for years, then using hundreds of GB certainly isn't abuse in my book.
Are we talking temporary throttling after having transferred hundreds of GB in a short time span (hours? days? do you know how fast they allow you to upload?) or throttling more or less forever once you store just hundredes of GB?
> Are we talking temporary throttling after having transferred hundreds of GB in a short time span (hours? days? do you know how fast they allow you to upload?) or throttling more or less forever once you store just hundredes of GB?
The former, from the people I've heard who run into it. These people are generally uploading tens of terabytes however.
Have you tried getting your data back out? Getting my wife's files back out of Crashplan was so bad we eventually settled for only getting the stuff that was absolutely vital.
I had ~4TB on a dedicated Gbit connection (sitting in a DC, not Google Fiber or something) and was averaging ~400GB/day, which is ~40Mbit. This was through duplicati though, I'm trying it now with rclone to see if it's a bottleneck elsewhere.
I've seen others saturate 300Mbit connections so it might be on my end.
EDIT: Just ran with rclone on the same server and I get about 30Mbit/s with small files (even with --transfers=16). With a single large file, I'm getting ~250Mbit/s. I think my issues in the past have been due to file creation overhead.
EDIT2: Ran again with numerous large files and --transfers=16 and I'm getting ~900Mbit. It seems the bottleneck is the api calls rather than the upload bandwidth.
If you don't abuse it it works great.