> and the technical people say "I just created a DO droplet and configured backup to Backblaze, easy and cheap!!".
That's very much missing the point. The non-technical option is inside that post: Backblaze. Do that twice, the second time with crashplan or carbonite, and you can keep your files safe without any trouble.
The real problem is that it can only protect the files on your computer. If you have data that's fed directly to google, there's no simple software to get it back out to where it can be backed up.
What if you're a bit cheeky, mount eg your Drive storage on a VM via one of the various 3rd-party filesystem-mounting systems out there, then run $backup_client on the VM pointed at the Drive local mountpoint?
Plenty of uncomfortable chances for failure, but a few heaped handfuls of error reporting would probably be mitigation enough.
Getting the initial clone done might be a little fun, you might need to actually download the Drive folder structure to somewhere spacious so you don't run into transfer ratelimiting for the initial upload.
That's very much missing the point. The non-technical option is inside that post: Backblaze. Do that twice, the second time with crashplan or carbonite, and you can keep your files safe without any trouble.
The real problem is that it can only protect the files on your computer. If you have data that's fed directly to google, there's no simple software to get it back out to where it can be backed up.