On Mon, Jun 30, 2014 at 2:55 AM, Holger Parplies <wbppc AT parplies DOT de> 
wrote:
>
> But I have to correct myself. Building an incorrect view can't be the cause,
> because then the file would simply be transfered (and logged as "pool" instead
> of "same"). Maybe we should think more closely about the rsync on the *remote
> end*, the host to be backed up. I'm not quite sure which side (of rsync) is
> responsible for doing the file list comparison, and I haven't really got the
> time to look right now, but failing to detect/signal unchanged files would
> result in exactly what you see.

I think what should be happening is that the remote side sends the
equivalent of a full directory tree listing, then both the backuppc
server and the remote walk the list comparing the contents with block
checksums.  In the case of fulls every file should be checked and
files that are the same should be logged as 'same' and linked into the
new backup tree.   This behavior doesn't make sense at all, but I
don't see how the remote side could miss sending the directory listing
for the files in the last backup, and then the server side should log
them as 'same', 'create', or 'pool'.

-- 
  Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
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/