This depends on how you've defined your share(s), and what method you're
using. SMB has problems with BackupFilesOnly and BackupFilesExclude
combinations, so if you use this, consider moving any "BackupFilesOnly" to
separate "SmbShareName" entries.
*$Conf{BackupFilesExclude} = undef; List of directories or files to exclude
from the backup. For Smb, only one of $Conf{BackupFilesExclude}
<http://backuppc.sourceforge.net/BackupPC-4.0.0.html#_conf_backupfilesexclude_>
and $Conf{BackupFilesOnly}
<http://backuppc.sourceforge.net/BackupPC-4.0.0.html#_conf_backupfilesonly_>
can be specified per share. If both are set for a particular share, then
$Conf{BackupFilesOnly}
<http://backuppc.sourceforge.net/BackupPC-4.0.0.html#_conf_backupfilesonly_>
takes precedence and $Conf{BackupFilesExclude}
<http://backuppc.sourceforge.net/BackupPC-4.0.0.html#_conf_backupfilesexclude_>
is ignored. This can be set to a string, an array of strings, or, in the
case of multiple shares, a hash of strings or arrays. A hash is used to
give a list of directories or files to exclude for each share (the share
name is the key). If this is set to just a string or array, and
$Conf{SmbShareName}
<http://backuppc.sourceforge.net/BackupPC-4.0.0.html#_conf_smbsharename_>
contains multiple share names, then 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 exclude file list is passed
into the X option. Simple shell wild-cards using "*" or "?" are allowed.*
Kris Lou
k...@themusiclink.net
------------------------------------------------------------------------------
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
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
