The point is to sync so if your local computer fails you can retrieve them. A situation could occur where your hard drive fails AND you're locked out of your Google Drive account.
I think his point was that this could be a way to backup certain critical data without having to think about it… but that their history of hands-off customer service & support may prevent that type of use.
User Commandment : Trust remote storage as a reliable source of back up in case of data loss.
If you violate this commandment, you will eventually lose users trust.
User Commandment : Once I sync the data, it must be available to me without any hassles on demand.
The usual technical lectures to users asking them to do things instead of making 'just work' don't fly.
That is why they ship TV's(with channels), Washing machines(with timers) and microwave ovens(with presets) without you having to bother too much about frequencies, volume/rotations and wave equations.
The user wants a product that 'works' the way he wants.
The existence of this new product does not make users more or less tech savvy.
If a user goes from 1 copy (hard drive), to 2 copies, then it's a net gain for their backups.
If a user goes from 2 copies (hard drive, some backup system), to 2 copies (hard drive, Google drive), then yes, arguably, it's a net loss for their backups, because they can simultaneously have a HD failure and get locked out of their Google account.
But arguably, they could live in Joplin, MO and both of their current backups could be toast.
Best to have three - hard drive, backup drive in a safety deposit box, and Google Drive if you like the convenience and access and cost, and don't mind the privacy implications.
I don't mind the privacy implications. Google doing something evil with user's data would be absolute suicide for them.
I don't like being pedantic, but a sync'ed copy isn't a backup. It might protect against hardware failure, but it won't help against accidental deletion or corruption.
I'm not sure if GDrive has file versioning/restoration built into it or not, but there is an important distinction to be made here.
Yes, but that's a two point failure. You don't engineer for two point failures until you're absolutely sure that you've covered all the single point failure cases, which basically means never.