BackupPC-users

Re: [BackupPC-users] Documentation on XferLOG

2014-03-14 04:54:30
Subject: Re: [BackupPC-users] Documentation on XferLOG
From: kpolberg <kpolberg AT kpolberg DOT net>
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Fri, 14 Mar 2014 09:51:58 +0100
On 03/12/2014 08:04 PM, Les Mikesell wrote:
> On Wed, Mar 12, 2014 at 1:36 PM, Holger Parplies <wbppc AT parplies DOT de> 
> wrote:
>> kpolberg wrote on 2014-03-10 11:32:35 +0100 [[BackupPC-users] Documentation 
>> on XferLOG]:
>>> I was looking at my XferLOG's and noticed some log lines which I could
>>> not understand.
>>>
>>>    pool     640   500/500      131068 2003.04.12 - 
>>> Påskeferien/100-0083_IMG.JPG
>>>    same     640   500/500      108343 2003.04.12 - 
>>> Påskeferien/100-0084_IMG.JPG
>>>
>>> Basically, what is the difference between "pool" and "same" ?
>> "same" means that it was an rsync backup and the rsync method found that the
>> file was identical to the same file in the reference backup and created a 
>> link
>> to that.
>> "pool" means that the file was transferred (possibly as an rsync delta, so
>> that does not necessarily mean a lot of data has crossed the network) and 
>> then
>> found to exactly match a file already in the pool. A link was created to the
>> pool file.
> Note also that your reference is the last full backup, not necessarily
> the 'last' backup, so a file that is changed or added in one
> incremental will still be changed/new in subsequent incrementals (and
> thus copied but matched in the pool) until another full run rebuilds
> the base.  Unless you are doing incremental levels.
>
I managed to only reply to Les, but for future reference I'm posting my 
answer to the list as well...

Thank you for the extensive feedback. Did a quick test by restoring a 
file from different backups and running md5sum. Couldn't find any 
differences, so I'm not quite sure what is going on here. But from your 
feedback, I guess this could be attributed to the checksumming in rsync. 
As the file is correctly linked to a file already in the pool. Basically 
what I was afraid of was bitrot or other issues.

Further on, looking back at Holger's reply. It seems there has been 
quite a lot of feedback regarding the various image viewing / editing 
tools I'm using regarding editing of at least EXIF data which isn't 
good. I would have at least expected these tools to keep the original 
and do the changes in a different version of the file. But this it seems 
is not the case.

For now my concerns are greatly reduced, atleast regarding the integrity 
of the RAID / File system wise. With regards to the tools I use for 
image editing and so on is a different story.

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
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/

<Prev in Thread] Current Thread [Next in Thread>