So, an interesting problem has presented itself, and I'm not quite sure how to solve it.
One of the (theoretically) nice things about using WAL-E to archive to S3 is that you can set up a lifecycle rule to move stuff to Glacier over time, so that old backups remain available while not paying the full S3 price. (And, of course, they can be deleted entirely after a while.) This works great... except for the timeline's .history file. Since S3 -> Glacier rules are based on creation date, eventually that file will be migrated to Glacier, and WAL-E restores start failing because it can't get at it. Since S3 lifecycle rules are path-prefix-based, there's no way to set a different rule for that file in particular. So, some thoughts: 1. I'm misunderstanding how this work, and there's an easy way that I've missed. 2. WAL-E could have an option to put the .history file in a different prefix, so different lifecycle rules could apply. Feels hackish. 3. A different solution that I'm missing. Thoughts? -- -- Christophe Pettus [email protected] -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
