BackupPC-users

Re: [BackupPC-users] Out of memory, backuppc_dump with rsyncd

2014-05-08 11:11:10
Subject: Re: [BackupPC-users] Out of memory, backuppc_dump with rsyncd
From: Les Mikesell <lesmikesell AT gmail DOT com>
To: pmaladjian AT hilaire DOT fr
Date: Thu, 8 May 2014 10:09:52 -0500
On Wed, May 7, 2014 at 8:52 AM, Philippe MALADJIAN
<pmaladjian AT hilaire DOT fr> wrote:
> Le 07/05/2014 15:06, Les Mikesell a écrit :
>
>> On Wed, May 7, 2014 at 1:22 AM, Philippe MALADJIAN
>> <pmaladjian AT hilaire DOT fr> wrote:
>>>>>
>>>>> My backuppc server a 6Go of RAM, I've 118 751 files for 9,1Go of data
>>>>> to
>>>>> save.
>>>>>
>>>> Rsync will send the entire directory tree to the server before both
>>>> systems walk the lists for the comparison, so it does take some
>>>> memory,  but your numbers look reasonable.  Just guessing - could the
>>>> target system have some other filesystems mounted or perhaps have
>>>> filesystem corruption or directory links that loop infinitely?
>>>>
>>> My structure is :
>>>
>>> +-------------+                               +-----------------+
>>> | backuppc | <-- rsyncd ---   | saved server |
>>> +-------------+                               +-----------------+
>>> |                                                           |
>>>        NFS (ext3)                                   NFS (ext3)
>>>               |
>>> |
>>>    +------------+ +-------------------------------------+
>>>     | /backup |                                 | /www/dev/ on NetApp NAS
>>> |
>>>    +------------+ +-------------------------------------+
>>>
>>> I do not think that will be a loop because the timeout occurs randomly
>>> and
>>> never on the same file or folder.
>>
>> Is backuppc walking into the .snapshot directories on the netapp?
>> Try a 'find . |wc -l' on the path rsyncd exports to get some idea of
>> the number of directory entries it sees and how long it takes.
>>
> # cd /path/to/dev
> # find . | wc -l
> 116 238
>
> My conf rsync module
>
> [wwwDev]
>          path = /path/to/dev
>          read only = false
>
> # mount
> 192.168.XXX.XXXX:/vol/www on /path/to type nfs
> (rw,noexec,nosuid,nodev,users,proto=tcp,rsize=32768,wsize=32768,timeo=60,retry=10,soft,addr=192.168.XXX.XXX)

That doesn't seem like it should be a problem, but I'd still look into
whether you are seeing the .snapshot directories.  If you are it might
help to exclude them.

-- 
   Les Mikesell
      lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
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/