On 2017-10-20 07:53, Michael Stowe wrote:
On 2017-10-20 01:56, Raoul Bhatia wrote:
On October 17, 2017 9:23:55 PM UTC, Michael Stowe
<[email protected]> wrote:
On 2017-10-17 14:01, Raoul Bhatia wrote:
Hi!
I use puppet for dynamic configuration management where clients
basically register with the BackupPC server for backup. I now face
the problem, that due to a config error/update/etc. a client might
be dropping out for a few days. This leads to BackupPC's host file
to be updated and BackupPC_nightly will clean the now unused
files.
They only related option I found right now is changin
$Conf{BackupPCNightlyPeriod}:
How many days (runs) it takes BackupPC_nightly to traverse the
entire pool. Normally this is 1, which means every night it runs,
it does traverse the entire pool removing unused pool files.
Other valid values are 2, 4, 8, 16. This causes BackupPC_nightly
to traverse 1/2, 1/4, 1/8 or 1/16th of the pool each night,
meaning it takes 2, 4, 8 or 16 days to completely traverse the
pool. The advantage is that each night the running time of
BackupPC_nightly is reduced roughly in proportion, since the total
job is split over multiple days. The disadvantage is that unused
pool files take longer to get deleted, which will slightly
increase disk usage.
Is there any other option to delay the cleanup that is caused due
to such misconfiguration?
Thanks, Raoul
Well, sure, you can always set the host to inactive, which as I
recall, will not only stop it from being backed up automatically but
suspend cleanup indefinitely.
You can also change the retention policies on a per-host basis,
which seems like it would be the sane thing to do, but I can't say I
completely understand your use case. Rephrasing myself: I'd like a
configurable grace period before the nightly cleanup removes orphans
from the pool. My current use case stems from a weird configuration
management module I am using, but I can also imagine some benefit
for other use cases as well.
I can't say I understand the need to control the cleanup independently
of the retention. You either want to keep a backup or you don't, it
seems.
Ah, *orphans*, got it, sorry.
In this case, I'd recommend that rather than removing them from hosts
altogether (which would result in the aforementioned cleanup) that
instead they are set to inactive.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
