3 ms·

To be fair, a good sync service with history is supposed to be a backup at the same time. I'm using git rather than dropbox but if I push something, it's there

by d0m 14y ago

To be fair, a good sync service with history is supposed to be a backup at the same time. I'm using git rather than dropbox but if I push something, it's there forever. So, I'd have to think that Dropbox being able to completely destroy files is a bug, not a feature. Maybe a more experienced dropbox user can correct me?

bonzoesc 14y ago
Why would a good sync service with history be a backup? They don't store a history indefinitely. Of course destroying files and history is a bug, but something that instantly replicates changes to those files from machine-to-machine shouldn't be considered a reliable way to recover them weeks or months later.
- tlrobinson 14y ago
  Dropbox does have "Packrat unlimited undo history" for $4/month. I wonder if he could have recovered these files if he had this option.
- Dylan16807 14y ago
  Does git push+pull not count as a "good sync service"?
itcmcgrath 14y ago
The difference is that a backup service shouldn't ever be able to corrupt your primary copy. Bugs happen. If a bug happens on the sync-ing service and it trashes your 'back-up'/history then syncs and trashes your primary copy, your toast. Sync'ing != Backup. They are for different problems and have different restrictions/pitfalls.
- whichdan 14y ago
  The thing is, Dropbox treats their version as the primary copy. For instance, I added several directories to Dropbox, and decided that I didn't want it syncing a few of them. I de-selected the directories under "Selective Sync" and it removed them from my computer - even though my computer was the original source.
- sdizdar 14y ago
  Yes, sync != backup [1]. I do agree with you but, I can tell you that selling backup service is harder than you think. Also as pointed by paper [2], the human error accounts for ~50% of all system failures. And the worst thing is that majority of users who accidentally delete data, don't even notice data loss until lost data is needed and they don't recollect doing something wrong. What I found out interesting that people (i.e., small business owners) will are scared of losing a credit card (even though you can call the bank and cancel your lost credit card and get a new one - inconvenience but not a big deal), but they will not backup critical company documents and data (even if they lose them the company will be pretty much closed - there is no "bank" to go to and get data back). [1] http://blog.cloudhq.net/post/33844549768/the-difference-in-data-sync-and-data-backup http://blog.cloudhq.net/post/33844549768/the-difference-in-d... [2] http://roc.cs.berkeley.edu/talks/pdf/HP.pdf http://roc.cs.berkeley.edu/talks/pdf/HP.pdf
  - itcmcgrath 14y ago
    Not sure it is harder than I think. Other than that, I haven't nothing else to disagree with. :)

by d0m 14y ago

bonzoesc 14y ago

Why would a good sync service with history be a backup? They don't store a history indefinitely. Of course destroying files and history is a bug, but something that instantly replicates changes to those files from machine-to-machine shouldn't be considered a reliable way to recover them weeks or months later.

tlrobinson 14y ago
Dropbox does have "Packrat unlimited undo history" for $4/month. I wonder if he could have recovered these files if he had this option.
Dylan16807 14y ago
Does git push+pull not count as a "good sync service"?

itcmcgrath 14y ago

The difference is that a backup service shouldn't ever be able to corrupt your primary copy. Bugs happen. If a bug happens on the sync-ing service and it trashes your 'back-up'/history then syncs and trashes your primary copy, your toast. Sync'ing != Backup. They are for different problems and have different restrictions/pitfalls.

whichdan 14y ago
The thing is, Dropbox treats their version as the primary copy. For instance, I added several directories to Dropbox, and decided that I didn't want it syncing a few of them. I de-selected the directories under "Selective Sync" and it removed them from my computer - even though my computer was the original source.
sdizdar 14y ago
Yes, sync != backup [1]. I do agree with you but, I can tell you that selling backup service is harder than you think. Also as pointed by paper [2], the human error accounts for ~50% of all system failures. And the worst thing is that majority of users who accidentally delete data, don't even notice data loss until lost data is needed and they don't recollect doing something wrong. What I found out interesting that people (i.e., small business owners) will are scared of losing a credit card (even though you can call the bank and cancel your lost credit card and get a new one - inconvenience but not a big deal), but they will not backup critical company documents and data (even if they lose them the company will be pretty much closed - there is no "bank" to go to and get data back). [1] http://blog.cloudhq.net/post/33844549768/the-difference-in-data-sync-and-data-backup http://blog.cloudhq.net/post/33844549768/the-difference-in-d... [2] http://roc.cs.berkeley.edu/talks/pdf/HP.pdf http://roc.cs.berkeley.edu/talks/pdf/HP.pdf
- itcmcgrath 14y ago
  Not sure it is harder than I think. Other than that, I haven't nothing else to disagree with. :)