>>>>I'm looking into cloud backup options for a small business, they'd be looking at backing up ~150GB.
>>>>
>>>>This will mainly be for secondary protection against disaster (fire, theft, earthquake etc.), they'll still have onsite backup to external media. Also for protection against CryptoWall-type malware.
>>>>
>>>>Anyone have any recommendations, for or against, the various providers?
>>>
>>>Against Cryptos this will only help if you do store distinct / incremental backups (so not overwriting) , and the filesystem should have no acces to it. Or the old backups might end up encrypted as well.
>>>
>>>IOW I think it's a good idea to have something on a non MS OS (just to protect it, makes it harder for maleware to have it several OS) that catches your "normal" backups and distribute them (encrypted with your key) to some external source. This might be some cloud service - or, as I do it, a cheap NAS on a friends location via VPN. So you will only loose what goes encrypted to "normal" backup.
>>>
>>>BTW, the normal Cryptos need some time (several days) to encrypt your HDD, but the files are encrypted evern on a server. If an incremental Backup starts growing w/o visible reason (file changed due to encryption by Crypto) you know what to do next.
>>>This is the Crypto on MS OS puts the data encrypted to SAMBA - but the linux machine will read raw data, the Crypto can not hook this side. -> Incremental Backup grows.
>>>
>>>You might argue that an MS Server might do the same, but the problems with MS accounts vote against that.
>>>
>>>My EUR 0,02
>>
>>All good points. In this case if the cloud backup retains former versions of files (either forever, or say 30/60/90 days) that's probably good enough.
>>
>>For this situation I don't think we need to go with heterogeneous OSs.
>
>Again, the problem is how you access the cloud. If it is like a networkshare - something you can reach through OSes API like MS cloud - then the Cryptor can readwrite this too. And the Cryptor will scan all reachable locations.
>
>I would recomend a four level grandfather-father-son solution of incremental backups, this has not to large backps, a restore needs only 1-4 datasets to restore. And you can go way back.

At this point I'm leaning towards CrashPlan. That accesses the cloud back end via an app on the server. It is not a network share or any sort of raw storage.

As long as the server itself doesn't get compromised I think the link to the CrashPlan cloud back end should be secure. Even if it does get compromised, I haven't heard of any malware that can emulate the communications protocol used.