|
|
|
|
|
by fauigerzigerk
938 days ago
|
|
The primary purpose of backup systems has always been to protect against data loss caused by failing/lost hardware or by accidentally deleting/overwriting data. Overwrites and deletes should largely be covered by versioning and soft deletes. Data loss caused by failing or lost hardware should be covered by a business relationship with a data storage service provider. This service provider role is what's new and different when we're talking about cloud storage. And this is why I reject a direct comparison with traditional backup systems. Yes you're right, the data should have been backed up to protect against data loss. But why is it the user's job to do that rather than Google's? I think users should be able to have a reasonable expectation that their backup needs are covered by using a cloud storage service with versioning and soft deletes. The fact that this expectation isn't met borders on false advertising. |
|
Sure, of course they should. But nothing in this life is perfect. Google engineers will roll out a configuration change that has unintended consequences that results in data loss. Or your account gets falsely flagged for abuse and you get locked out. Or your computer gets infected with ransomware that accesses your cloud sync, creating duplicate encrypted files, deleting the originals, and emptying the trash -- so much for your version history.
Don't put all your eggs in one basket, create your own backup. It's "the user's job to do that rather than Google's" because at the end of the day, other people mess up, and it's your personal responsibility to safeguard against that if you want to protect against losing your data. It's always been this way and always will be.