Hi Christophe What I'm doing for this is to enable versioning on the bucket, and setup the lifecycle rule so that only old versions get moved to glacier (they released that feature recently). Then I've got wal-e setup to delete old backups after a period - when the file is deleted from S3, the file is actually still there because of the versioning, and then the old version gets moved over to glacier after a while.
This way the .history file never gets moved to glacier, since it's not deleted by wal-e, but the logs and old base backups are. Jordan On Wednesday, September 17, 2014 5:43:39 AM UTC+12, Christophe Pettus wrote: > > > On Sep 16, 2014, at 10:41 AM, Daniel Farina <[email protected] > <javascript:>> wrote: > > > I am not inclined to add any options to tweak the storage layout. I'd > > rather have a fallback for backwards compatibility and otherwise have > > new installations to write things in the new format. > > No strong feelings on my end. It's my ox that's being gored, so I'm happy > to take a pass at it. Would WAL-E just probe both locations for the > metadata? > > -- > -- Christophe Pettus > [email protected] <javascript:> > > -- 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.
