Re: [BackupPC-users] backuppc ignores value of BackupFilesOnly; archives entire /

[Bowie B. <Bowie_Bailey@BUC.com>]

On 1/18/2011 9:51 AM, itismike wrote:
> ----
> Normally you would only use the sharenames as the starting points of what you
> want to back up and it defaults to including everything. It doesn't make much
> sense to tell the client to walk the whole directory tree when you only want a
> specific directory. But the way it is used depends somewhat on the xfer method.
> If you use rsyncd (or smb), it has to match a module configured on the client,
> while it can be any directory with rsync or tar. Also, I think some of the xfer
> methods can't handle both include and exclude lists.
>
> Les Mikesell 
> ----
>
> I understand that it defaults to include everything. But the parameter 'BackupFilesOnly' allows the administrator (or a user - shudder the thought) to narrow that definition. If BackupPC simply ignores this value unless it is entered again in a different location this is a very loose interface.
>
> I don't intend to sound terse toward those reaching out to help me; only point out that any newcomer to this program is going to hit this same wall every time. According to the documentation I am using the parameters correctly based on my transfer method (rsync). Where is the best place to open a bug or wishlist item for BackupPC?

It does tend to be a bit non-intuitive at first.  The sharenames define
the trees that are being backed up.  You can then use the
BackupFilesOnly and BackupFilesExclude to modify those shares.  The key
name is always the same as the sharename (or '*' if it applies to all
shares).

For Example:

$Conf{RsyncShareName} = [
    'A',
    'B'
];
$Conf{BackupFilesOnly} = {
    'A' => [
        '/first/backup/dirA',
        '/second/backup/dirA'
    ],
    'B' => [
        '/first/backup/dirB',
        '/second/backup/dirB'
    ]
};
$Conf{BackupFilesExclude} = {
    '*' => [
        '/global/exclusion'
    ]
};

-- 
Bowie