Thanks Adam
that makes a lot of sense. Trying now and will confirm if this works. I
do find it really odd that the same config works on one machine but not
another though.
regards Tom
On 12/10/14 23:34, Adam Goryachev wrote:
>
> On 13/10/14 08:54, Tom Fallon wrote:
>> Thanks Doug
>>
>> by my limited understanding, the * wildcard in my example below would
>> mean the system would exclude any directory called "proc" or "sys" etc
>> regardless of the share, whereas what I think should be used is
>> ryncshare = / and then specify the directories under there explicitly
>> which I had done.
>>
>> Amending to '*' => [ in the config.pl file resulted in same behaviour
>> I've been seeing all along.
>>
>> In your config I'd expect it to be excluding file types by extension
>> rather than directories.
>>
>> I could try '*/proc' etc I guess but think thats a bandaid approach and
>> would really like to get this working the way its supposed to based on
>> the documentation.
>>
>> regards Tom
>>
>> On 12/10/14 22:32, Doug Lytle wrote:
>>> Tom Fallon wrote:
>>>> $Conf{BackupFilesExclude} = {
>>>> '*' => [
>>>> 'proc',
>>>> 'sys',
>>> My list shows:
>>>
>>> $Conf{BackupFilesExclude} = {
>>> '*' => [
>>> '*/Cache',
>>> '*.mp3',
>>> '*.MP3',
>>> '*.m4a',
>>> '*.M4A',
>>> '*.m4v',
>>> ]
>>> };
>>>
> $Conf{BackupFilesExclude} = {
> '/' => [
> '/proc/'
> '/tmp/'
> ]
> };
>
>
> The '/' is the share name, so using * just means all shares, since you
> only have one share, then there is no difference.
> I would suggest using /proc/ (trailing slash) because then you will
> backup the directory without the contents. After a full restore, you
> will need the directory /proc to exist, or else mounting /proc will
> fail, same with /tmp etc.
> Also, be careful when excluding /var/log or similar, as some software
> will want subdirectories to exist.
>
> Also, you could consider add --one-file-system to the rsync command
> which will automatically skip any other mounted drives/partitions.
>
> Finally, if it is still not working, please post the full config file,
> along with the log from a full backup run (at least the start where it
> shows what command was sent, and a sample where it has backed up some
> files that you had requested).
>
>
> Regards,
> Adam
>
--
Tom Fallon
1033 Aikenhead Road
Glasgow
G44 4QT
Tel: 0141 5697824
Mob: 07909 754 170
Skype: fallontom
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
