Hi,
Steve M. Robbins wrote on 2011-10-29 21:29:49 -0500 [[BackupPC-devel] doc patch
for $Conf{BackupFilesExclude}]:
> I was confused about how BackupFilesExclude worked with rsync[1].
> Attached is a patch that documents what I learned experimentally.
> [...]
> diff -u -r BackupPC-3.2.1.orig/doc/BackupPC.pod
> BackupPC-3.2.1/doc/BackupPC.pod
> --- BackupPC-3.2.1.orig/doc/BackupPC.pod 2011-04-24 22:31:55.000000000
> -0500
> +++ BackupPC-3.2.1/doc/BackupPC.pod 2011-10-29 15:33:52.707308813 -0500
> @@ -3410,7 +3410,7 @@
> the setting is assumed to apply to all shares.
>
> The exact behavior is determined by the underlying transport program,
> -smbclient or tar. For smbclient the exlclude file list is passed into
> +smbclient or tar. For smbclient the exclude file list is passed into
> the X option. Simple shell wild-cards using "*" or "?" are allowed.
>
> For tar, if the exclude file contains a "/" it is assumed to be anchored
> @@ -3424,6 +3424,11 @@
> the directory name: a trailing "/" causes the name to not match
> and the directory will not be excluded.
>
> +For rsync or rsyncd, omit the share name in the exlusion pattern.
> +When backing up "/home", for example, the exclusion
> +"/home/steve/.mozilla" will not match, but "steve/.mozilla" will
> +match.
> +
> Users report that for smbclient you should specify a directory
> followed by "/*", eg: "/proc/*", instead of just "/proc".
this is not specific to rsync. Personally, I'd rather stress the reference to
the man pages (or info pages, as far as tar is concerned ...). If you look at
rsync(1), you'll agree that the matter of specifying exclude and include
patterns is rather complex. This is clearly beyond the scope of config.pl (or
BackupPC.pod). On the other hand, if you actually read the rsync man page,
you'll understand the concept of the transfer root, and it will be quite
natural that you need to specify your excludes (and includes) relative to it.
A general remark along the lines of "Excludes and includes are always relative
to the respective share name" might be helpful, though.
Regards,
Holger
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
