4 ms·
I use a combination of Dropbox and S3. I have my MacBook and a Linux server linked to my Dropbox account. So changes in my documents are synced to my Linux. M
by g-garron 14y ago
I use a combination of Dropbox and S3.
I have my MacBook and a Linux server linked to my Dropbox account. So changes in my documents are synced to my Linux.
My Linux run three cron-jobs. One daily, one weekly and another monthly. The command is.
s3cmd sync --delete-removed ~/Dropbox/documents/ s3://backup-daily/
There are buckets for weekly and monthly too.
Note: the command is not exactly like that, check the man page.
That way I have backed up all my documents very cheap.
- ghshephard 14y agoOne thing to be a little careful of - you are sending all of your data to S3, which is, of course, the backing store for Dropbox.
- sintaks 14y agoDropbox stores their stuff in S3 a little different. It's not a 1:1 correspondence between user files and objects under Dropbox's S3 account. The fact that they use S3 as their backing store means very little. It certainly sounds good to have S3 in back when you talk about scalability and durability, but 1) they could just as easily use something else, and 2) depending on their sharding strategy, a single lost object could impact multiple files at the user level.
- ghshephard 14y agoRight - the point I was trying to make, is he was putting all his eggs in one basked. If anything catastrophic happened to S3, he might lose both his S3 as well as his Dropbox backups. If you are going to the effort of having dual-backup systems, may as well try and find something that can't be impacted by a single disaster.
- sintaks 14y agoAh, right - definitely.
- DeepDuh 14y agoWait, do I understand this correctly: You sync your dropbox to S3? Do you overwrite your previous daily when you do so?
- g-garron 14y agoYes I do it, I have the weekly and monthly. And yes, I might have daily-monday / daily/tuesday.... and so on, and it would work better, but this way works for me. There is a lot of room for improvement, and it is not hard to implement with cron-jobs and more buckets.
- narsil 14y agoYou could try adding objects with the date in their names to a 'backup' bucket rather than create separate buckets for each backup. S3 also supports object expiration, so you can set your daily backups to expire after 7 days and weekly backups to expire after 4 weeks, for example.
- DeepDuh 14y agoDo you know about worst case analysis? Let's say your data loss occurs on the Sunday, 31th of a month at 23:55 and then gets synched across all your S3 backups (or it could occur at some point before that but you don't notice it). And poof goes your data.
- tedunangst 14y agoTHIS. I'd say at least half of the time I went to retrieve a good revision of a file from backup, it was already too late and the backup was trash as well.
- sintaks 14y agoHe could just turn on object versioning.