On Thu, 2019-03-14 at 20:33 -0700, Graham Percival wrote:
> On Fri, Mar 15, 2019 at 12:07:57AM +, Bob Eager wrote:
> > On Thu, 14 Mar 2019 16:28:25 -0700
> > Craig Hartnett wrote:
> >
> > > Thanks, but wow, that seems unnecessarily complicated and
> > &g
On Thu, 2019-03-14 at 20:21 -0700, Graham Percival wrote:
> Here's my solution, using the --archive-names option (new in
> 1.0.38, 2018-July-15, so longtime users might not know it exists).
>
> I'm deleting any archive names that match "zeros-100*" because
> they're left-over from some debugging I
On Fri, 2019-03-15 at 00:07 +, Bob Eager wrote:
> Before re-inventing the wheel, take a look at ACTS:
>
> https://www.tarsnap.com/helper-scripts.html
Thanks Bob, but as I said in my original post I'd already skimmed the
sources of some of the helper scripts for the answer to my question. I'
On Thu, 2019-03-14 at 17:39 +0200, hvjunk wrote:
> Pull the whole list of archives, then grep for those you want, and do a
> multiple delete action: Beware, it could take easily an hour for large number
> of archives (In my case dailies) where I delete and leave weeklies/monthlies
> every 3-6mon
Hi all,
I've skimmed the sources of some of the "helper scripts" that offer
archive rotation (and, of course, done a web search), but I can't seem
to figure out how to use wildcards to delete Tarsnap archives. The
following attempts (to delete all archives from November 2018 using the
default nami
tain on that day".
>
> - Want to see it from 3 days ago? Restore that archive.
> - Want to see it from yesterday? Restore that archive.
> - Do you care about the contents from 2 days ago? No? Ok, delete that
> archive.
>
> Your ability to see the version from 1
18-11-24 at 12:30 -0800, Graham Percival wrote:
> On Fri, Nov 23, 2018 at 05:33:03PM -0800, Craig Hartnett wrote:
> > Hi Graham,
> >
> > Thanks for your reply. Sorry for not getting back to you sooner.
>
> No problem. I'm glad it worked out!
>
> > The
+, Jamie Landeg-Jones wrote:
> 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?
> &
Hi Jamie,
A thousand apologies for not acknowledging your email almost four months
ago. You did a great job of educating me, and bringing to my attention
the -q switch. Thanks.
Craig
On Sat, 2018-11-24 at 16:01 +, Jamie Landeg-Jones wrote:
> Craig Hartnett wrote:
>
> >
tem you will need
> more drives, tapes whatever with time).
>
> Niels
>
>
> > On 24. Nov 2018, at 04:04, Craig Hartnett wrote:
> >
> > Hi again,
> >
> > OK, so I did read that I'm supposed to forget everything I know about
> > back-ups,
Hi Bob,
Thanks for your reply.
On Sat, 2018-11-24 at 09:48 +, Bob Eager wrote:
> On Fri, 23 Nov 2018 17:35:06 -0800
> Craig Hartnett wrote:
>
> > In all test cases I used the following command:
> >
> > tarsnap -x -f ARCHIVE media/USER/PATH/DIRECTORY
&g
Hi again,
OK, so I did read that I'm supposed to forget everything I know about
back-ups, but frankly that wasn't much. :) Not that I know nothing, but
it hasn't been something I've spent a *lot* of time thinking about.
But as I think about Tarsnap, deleted files, rotating/deleting archives,
dail
Hi there,
This email was going to be a (mild) complaint about restore times, but
then I noticed an odd thing: If I restore a directory with about 30
full-size, full-resolution images, the directories in the path to the
directory I restore are all created within about 45-90 seconds, and then
the fi
Hi Graham,
Thanks for your reply. Sorry for not getting back to you sooner.
On Mon, 2018-11-12 at 11:05 -0800, Graham Percival wrote:
> I'm pretty certain that your first upload will be limited by your upload
> speed.
Yes, you are right, of course. I think I was just surprised that the dry
run
Hi Graham,
On Thu, 2018-11-08 at 18:07 -0800, Graham Percival wrote:
> Welcome!
Thanks, and thanks for your reply.
> Careful there! "--exclude" only accepts a single value.
OK, that was clear in the config file, but not in the man page.
> "tarsnap -c -f foo" doesn't work, even if we
Hi there,
Just signed up and put $50 in my account (sorry, did $35 then $15
because I forgot to account for upload *and* storage costs), but I'm
stuck. Yesterday I did eventually calculate my expected usage using the
--dry-run parameter, but only by running a series of discrete commands
(e.g., tar
16 matches
Mail list logo
