News for hackers. Stuff that matters.
Re:Amazon Glacier by g-garron on Tuesday August 21, 2012 @09:28AM (#4412578)
Yes 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.

Re:Amazon Glacier by DeepDuh on Tuesday August 21, 2012 @07:00PM (#4415235)
Do 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.

Re:Amazon Glacier by tedunangst on Tuesday August 21, 2012 @08:25PM (#4415496)
THIS. 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.
Re:Amazon Glacier by sintaks on Wednesday August 22, 2012 @01:45AM (#4416208)
He could just turn on object versioning.
Re:Amazon Glacier by narsil on Tuesday August 21, 2012 @06:33PM (#4415141)
You 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.