Re: [BackupPC-devel] Getting excludes right...

[Craig B. <cba...@us...>]

In addition to getting the exclude settings right, in 4.x if you add an
exclude for an already backed-up file or directory, the file or directory
won't be backed up (correct), but won't get deleted on the server, so it
will be still be visible in the most recent filled/full backup (incorrect).

If that's an issue you have, you can add the --delete-excluded option to
$Conf{RsyncArgs} to fix this.  I pushed that change to git in a few days
ago and it will be in 4.1.2.

Craig

On Sat, Apr 29, 2017 at 7:47 AM, Michael Stowe <ms...@ch...>
wrote:

> On 2017-04-29 08:05, Richard Shaw wrote:
> > Ok, getting a little closer... I changed the configuration to:
> >
> > $Conf{BackupFilesExclude} = {
> >   '*' => [
> >     '/home/*/.cache',
> >     ''
> >   ]
> > };
> >
> > And ran the dump from the command line and got:
> >
> > --exclude=/home/\*/.cache --exclude= <host>:/home/<user>/
> >
> > It seemed to generate two excludes but the second one seems to be
> > malformed with the space after the = and I'm not sure it's even
> > needed...
> >
> > Thanks,
> > Richard
>
> ... which begs the question, why did you include it?  Why not just use
> the first exclude, which seems perfectly valid, i.e.
>
> $Conf{BackupFilesExclude} = {
>     '*' => [
>       '/home/*/.cache'
>     ]
>   };
>
> I'm genuinely baffled.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-devel mailing list
> Bac...@li...
> List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
> Wiki:    http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>