Upload & Sell: Off
An update on my experience.
After a couple of successful days of backing up to CrashPlan, I decided to give the iOS app a shot. I could not get it to connect, so I reached out to their support who were responsive and friendly. Ultimately, he had to pass me on to a developer because he could not provide a solution. During this interaction, I noticed my MacBook has stopped backing up entirely and was "Waiting for connection...", so I added this to my support ticket. The developer responded with some suggestions as to how to test the connection and check my network, none of which helped. And quite frankly, if I have to start running Terminal commands to get your application working on a brand new machine that every single other thing I've installed works flawlessly on, I've already lost interest and faith.
During this time no variables on my end changed, my network was up and running, I tried multiple networks, reinstalling, etc. to no avail. Periodically I could get it to "Synchronize blocks" which would take 1+ hour and if I waited it would begin uploading. But if I interrupted it and say, slept my MacBook, it would be the same issue all over again. I'm not sure what happened or what changed, but it did not instill much confidence in their service.
Out of curiosity, I decided to reinstall Backblaze. A quick install and I was backing up instantly on the same network CrashPlan wouldn't even connect through. Despite my recent frustrations with them and the 30 day data retention limitation, I can attest that my backups have been reliable and painless for 2+ years. Set and forget, which is what I'm looking for in an cloud backup solution. So it looks like I am once again a Backblaze user.
A couple of additional notes:
1) The upload speed I was quoting for CrashPlan was an effective rate including local compression, not an actual upload speed.
2) Due to being Java based, CrashPlan consumes 150-250mb of RAM at all times, while Backblaze is currently only using 17mb while backing up. A huge difference.