On Wed, May 9, 2012 at 11:01 AM, Matthew Baker <matt.baker AT bristol.ac DOT 
uk> wrote:
>>
> By looking at the size of directories growing under the clients new
> directory I could see that /proc was most active. This particular client
> didn't have a specific BackupFilesExclude config so I've set a global
> default to:
>
> $Conf{BackupFilesExclude} = {
>   '*' => [
>     '/tmp/*',
>     '/proc/*',
>     '/sys/*'
>   ]
> };
>
> Restarted and retried this client and it finished an incremental run! =]
>
> Over half of the other clients have /proc already excluded. Will see
> over night if this helps those that don't.
>

I generally use --one-file-system as an rsync option which will keep
it from wandering into /proc and /sys as well as any nfs or iso mounts
that are accidentally in the path.   Of course if you do that, you
have to add explict 'share' entries for each mount point that you want
backed up and be careful to add new ones as needed.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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/