[Borgbackup] Pruning Schedule Not Working as Expected

Blu Finney me at blufinney.com
Thu Mar 15 02:57:56 EDT 2018


Yep, in addition to a couple other fine tunings.  After spending some
time thinking about it I used the following.  After pruning with these
new settings the results matched what I was ultimately shooting for.

    keep_within: 3H
    keep_hourly: 16
    keep_daily: 7
    keep_weekly: 4
    keep_monthly: 12
    keep_yearly: 5


-----Original Message-----
From: Elladan <elladan at eskimo.com>
To: Blu Finney <me at blufinney.com>
Cc: borgbackup at python.org
Subject: Re: [Borgbackup] Pruning Schedule Not Working as Expected
Date: Wed, 14 Mar 2018 23:15:00 -0700

I'm not sure what your exact needs are, but my quick impression is
that just removing the --keep-minutely option and keeping the rest the
same will probably give you something approximating what you want.


On Wed, Mar 14, 2018 at 9:17 PM, Blu Finney <me at blufinney.com> wrote:
> You'll have to pardon me.  After thinking about this more I can
> understand why the "snapshot" mentality really doesn't apply here.
> 
> I'll have to spend some time doing some math to get the results I'm
> looking for.
> 
> Thanks for your help.
> 
> 
> -----Original Message-----
> From: Blu Finney <me at blufinney.com>
> To: Elladan <elladan at eskimo.com>
> Cc: borgbackup at python.org
> Subject: Re: [Borgbackup] Pruning Schedule Not Working as Expected
> Date: Wed, 14 Mar 2018 21:06:21 -0700
> 
> Thank you for the simple explanation.  I totally misunderstood the
> documentation - I think because of my "snapshot" mindset (like good
> ole
> sun zfs).
> 
> Here I thought "--keep-hourly 24" meant keep archives from the past
> 24
> hours, and "--keep-minutely 60" meant keep archives from the past 60
> minutes, and so on.
> 
> Is there a way to implement the snapshot mentality using "--keep-
> within"?
> 
> e.g.
> --keep-within 60M --keep-within 24H --keep-within 7D ...
> 
> 
> Sorry for the sophmoric question, I'm really having a hard time
> wrapping my head around the "--keep-hourly X" way of thinking in
> order
> to achieve the results I'm looking for.
> 
> 
> -----Original Message-----
> From: Elladan <elladan at eskimo.com>
> To: Blu Finney <me at blufinney.com>
> Cc: borgbackup at python.org
> Subject: Re: [Borgbackup] Pruning Schedule Not Working as Expected
> Date: Wed, 14 Mar 2018 19:42:22 -0700
> 
> On Wed, Mar 14, 2018 at 7:01 PM, Blu Finney <me at blufinney.com> wrote:
> > 
> > Hi,
> > 
> > I've been using Borg backup since Mar 5th and am not clear why the
> > pruning schedule isn't working as expected.
> > 
> > Details:
> > - Running backup every 3 hours (8 archives created per day)
> > - Pruning command used: borg prune :: --keep-within 3H --keep-
> > minutely
> > 60 --keep-hourly 24 --keep-daily 7 --keep-weekly 4 --keep-monthly
> > 12
> > --
> > keep-yearly 1 --prefix {hostname}- --debug --stats --list
> > 
> > Using these prune settings I was expecting some of the 8 daily
> > archives
> > to have been pruned by now.  Yet none have been pruned.
> > 
> > Have I misunderstood or misconfigured something?
> 
> You've basically asked borg prune to do this (rules applied one after
> another):
> 
> 1. Keep all archives in the last 3 hours.
> 2. Keep the last 60 archives, but not more than one per minute.
> 3. Keep the last the last 24 archives, but not more than one per
> hour.
> 
> And so on. So basically, you've asked it to keep a very large number
> of archives.
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20180314/3ec41779/attachment.sig>


More information about the Borgbackup mailing list