10 ms·
Sync is not backup. Sync is not backup. Sync is not backup. My strategy: a big external drive used for Time Machine, and a subscription to Backblaze. Both of
by egypturnash 12y ago
Sync is not backup.
Sync is not backup.
Sync is not backup.
My strategy: a big external drive used for Time Machine, and a subscription to Backblaze. Both of these are all about retaining multiple versions, recovering from accidental deletion, and continuously backing up in the background. Dropbox is about syncing stuff between computers.
- bruceboughton 12y agoI too am a Backblaze customer but beware: backups of deleted files are deleted after 30 days.
- TheLoneWolfling 12y agoYour definition of backup...
- bruceboughton 12y agoWhich is why I don't solely use Backblaze (fast recovery, medium level of trust). I also backup the same data to Glacier-class S3 (slow recovery, high level of trust) and Time Machine (v. quick recovery, same-site risk).
- lh7777 12y agoOne of the reasons I switched to Crashplan. Their Java client is pretty terrible performance-wise, but it's still the best cloud backup I've tried.
- smackfu 12y agoThat's kind of surprising given how their hardware model is setup, with pods of HDDs that are filled up and then essentially archived away. I guess the amount of space freed up is enough that it makes sense to open those pods back up for writing.
- egypturnash 12y agoHuh, I didn't know that. My first line of 'oh shit I deleted a thing' is Time Machine, since it's right there next to my external monitor and won't require waiting for a download.
- gabemart 12y agoDropbox keeps deleted files and previous versions of files for 30 days. With Packrat, a free feature for all paid accounts, Dropbox keeps deleted files for the lifetime of the account. How is Dropbox not a backup provider? It may not be a very good backup provider, depending on your point of view, but it clearly markets itself as a backup provider ("your stuff is always safe in Dropbox and can be restored in a snap"), is used by its users as a backup provider, and has the features of a backup provider.
- jackweirdy 12y agoBackups should be read only. If I can delete parts of a backup, it's just as susceptible to the same human mistakes that make them necessary in the first place.
- _delirium 12y agoBy that definition, most corporate backup systems aren't backups! It's pretty common to overwrite old tape backups with newer backups, and yes, that does mean you need to be organized enough to make sure you don't accidentally overwrite the only backup of something.
- snowwrestler 12y agoMaybe a better way to put it is that backups are isolated from current "production" data operations. Backups are not invulnerable, so yes, it's still possible to overwrite the backups, but that involves engaging the backup system specifically. Just doing file operations or settings changes on the production system won't do it. Dropbox is not isolated from production data operations. In fact the whole point is to synchronize production data operations as fast as possible. That makes it dangerous. (This does not excuse the bug is this story; sync setting changes should be obviously be atomic transactions that are confirmed on the server.)
- jackweirdy 12y agoYeah; that's a better way of putting it. rm -rf'ing my production box's hard drive shouldn't nuke the backups.
- deleted 12y ago[deleted]