On 3/1/2010 3:18 PM, anethema wrote:
>
>
> Les Mikesell wrote:
>>
>> Pool matching is done based on the file content, not the name. Backuppc
>> won't know what you mean by 'corrupted', but if the content is
>> different, it becomes a different pool entry, not linked to existing
>> ones with different content.
>
>
> Yeah I was just worried that if you end up with some FAT/HDD issues on your
> backup drive, and it corrups one file in the pool, it will corrupt it for
> every single full or incremental backup that you have, requiring the next
> backup to fix it.
>
> So the only difference between incremental and full is the method of veryfing
> if the data has changed? On the backup drive they end up identical anyways
> (except a full is like a filled incremental) ?
Yes - it takes a bit longer to do an rsync full because it reads all the
data on the target, but it doesn't take much more bandwidth. And a full
becomes the base comparison for the next run where incrementals will
normally transfer all changes from the last full unless you have set up
incremental 'levels'.
--
Les Mikesell
[email protected]
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
