> No, not at all. As Albert said, it's more of a
> --assume-modified-if-newer-than
> option (although "--assume-potentially-modified-if-newer-than" would be
> closer).
--assume-potentially-modified-if-newer-than-or-equally-new-as? ;)
On Fri, 24 Jan 2014 11:29:22 -0800
Colin Percival wrote:
>
On 01/23/14 08:56, Daniel Staal wrote:
> --As of January 23, 2014 8:32:14 AM -0800, Colin Percival is alleged to have
> said:
>> That will effectively disable the "recognize when files haven't changed"
>> functionality, which will force Tarsnap to re-read files which it might
>> otherwise have not
> That will effectively disable the "recognize when files haven't changed"
> functionality, which will force Tarsnap to re-read files which it might
> otherwise have not bothered to re-read.
That's the hint I needed to understand how it works.
Daniel, if I am not mistaken, the idea is to flag tho
--As of January 23, 2014 8:32:14 AM -0800, Colin Percival is alleged to
have said:
Point it at anything with a modification time <= when the snapshot was
created. Obviously anything inside the snapshot will have this
property; as will a file you create prior to creating the snapshot.
Colin,
On 01/23/14 08:31, Albert Peschar wrote:
> Thanks Nick, your snippet is very helpful.
>
>> Point it at anything with a modification time <= when the snapshot was
>> created. Obviously anything inside the snapshot will have this property;
>> as will a file you create prior to creating the snapshot
wrote:
> > I've been using tarsnap for some months to do all kinds of backups.
> > Now, I'd like to use tarsnap to archive ZFS filesystem snapshots. What
> > is unclear to me is whether and how I should be using the --snaptime
> > option.
>
> Point it a
On 01/23/14 03:43, Albert Peschar wrote:
> I've been using tarsnap for some months to do all kinds of backups.
> Now, I'd like to use tarsnap to archive ZFS filesystem snapshots. What
> is unclear to me is whether and how I should be using the --snaptime
> option.
Point
stem snapshot #1
t=5.: filesystem snapshot #2 is created
t=54321.: tarsnap is run against filesystem snapshot #2
since both snapshots will show the file with an mtime of 12345. Tarsnap
uses the snaptime marker to identify cases like this.
In short: It's a sneaky race condition whic
Hi all,
I've been using tarsnap for some months to do all kinds of backups.
Now, I'd like to use tarsnap to archive ZFS filesystem snapshots. What
is unclear to me is whether and how I should be using the --snaptime
option.
From the manual:
--snaptime file
(c mode
