So obnam --keep=14d,3m,1y is equivalent to expire_backups.py 14 90 365 ?
On Monday, April 20, 2015 at 6:26:45 PM UTC+2, Nikolaus Rath wrote: > > [Quoting repaired] > > On Apr 20 2015, Viktor Szépe <[email protected] <javascript:>> wrote: > > On Saturday, April 18, 2015 at 10:53:05 AM UTC+2, Viktor Szépe wrote: > >> > >> Is there a way to upload only changed file, thus doing incremental > backup? > >> My usecase is making backup of a website that has 1 or two new files > per > >> backup. > > > > Excuse me that was a wrong question. > > The right one is: Will s3ql read the file's contents to determine > whether > > it has change or reads only the file's metadata (mtime, size etc.)? > > I don't think that's the right question either. > > S3QL is a file system. When a client application (like your backup > program) tells it to write data to a file, it checks if it already has > identical data stored and (if so) saves only one copy. > > There is no way for S3QL itself to compare mtime and size. S3QL does not > know when a file has reached its "final" size or mtime, and the mtime is > the time of last write, i.e. when S3QL receives a write request it is > always the current time. Finally, S3QL also has no idea which other file > to compare any of this against. > > What you want is a feature of the backup program. For example, if you > use rsync it will only copy a file if its attributes have changed. Look > at http://www.rath.org/s3ql-docs/contrib.html#s3-backup-sh for an > example. > > > Best, > -Nikolaus > > -- > GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F > Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F > > »Time flies like an arrow, fruit flies like a Banana.« > -- You received this message because you are subscribed to the Google Groups "s3ql" 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.
