Re: Rotating back-ups, removed files, etc.

Craig Hartnett wrote: > Hi again, > > So if I delete my initial archive today, Tarsnap will realise that it > has to upload pretty much everything -- not everything, but almost > everything -- again, right? > > And what if I delete a file -- any file -- on my hard drive that has > been backed up

Re: Odd thing about restore times

Craig Hartnett wrote: > Yet in both cases, the command does not exit for about 16-21 minutes, > which is what was going to lead me to complain. However, the actual > restore was done about as quickly as one would expect. Hi. tarsnap follows the "tar" standard. In fact, it actually uses the bsd

Re: tarsnap nuke and the web interface

Colin Percival <cperc...@tarsnap.com> wrote: > On 07/16/17 04:37, Jamie Landeg-Jones wrote: > > (I sent this a week or so ago, but the message never appeared) > > Were you subscribed to the list? Messages from addresses not subscribed get > filtered into a moder

Re: Question about mitigating large storage costs in case of ransomware

> I just started using tarsnap, and I was wondering if there exists an > option (or the potential interest in developing an option) to put a cap > on an archive size. [ ... ] > The closest thing I could find is the --maxbw option; is there a > corresponding option for archive size that I'm not

Re: Question about mitigating large storage costs in case of ransomware

Actually, re-reading your message, I now think I misunderstood, and you want to limit the size of the individual virtual archive, rather than the literal size of data-transfered? J.

Re: tarsnap: Decrypting file would require too much memory

Colin Percival wrote: > Maybe we should add a --passphrase-force option which overrides tarsnap's > attempt to autodetect whether there's enough memory. (Does anyone have a > preference for what the option is named?) After lately spending some time on Unix portability

Re: Monitor ongoing upload?

This isn't really necessary for the case of copy files to a different device -- it's specific to the case of filesystem snapshots (as in UFS and ZFS) because those will keep the timestamps from the underlying file system. Oh I see. Thanks. Also, I realise I misread the original question - I

Re: Exclude patterns

*** Can config files include other files? I don't know off hand, but if I wanted to know, I'd try it :-) Don't forget the '--dry-run' option to tarsnap, coupled with '--verbose' lets you test out all your changes/excludes/includes/nodumps etc. without actually spending time/money/screwup-risk

Re: Mixing include and exclude patterns in tarsnap.conf

Bob Williams li...@barrowhillfarm.org.uk wrote: If I remove all those include directives, then it runs as I expect, lots of lines beginning with 'a', and apparently backing up all the non-excluded stuff in /home/bob (which is what I want) and the whole of /etc (which I don't want). I could

Re: Exclude patterns in tarsnaprc

N! If you remove the leading '/' off your exclude pattern, it will exclude any match of that directory in the tree. Even excludes of 2 or more directory levels, e.g. --exclude usr/src would match usr/users/jamie/usr/src To exclude reliably, you have to 'anchor' the path to root by

Re: Exclude patterns in tarsnaprc

Bob Williams li...@barrowhillfarm.org.uk wrote: Jamie, Many thanks for your timely intervention and very clear explanation. Perhaps the manpage could include some examples? No problem! Applogies if it came across a bit ranty, I hadn't slept for 2 days, and my OCD was running high. I'm calm