> Backuppc does a hash over some portion of the file contents 
> and uses that as the name in the pool directory (cpool if 
> compression is on but the hash is for the uncompressed data). 
> If this name doesn't exist, it is created as a link to the 
> inode of the new file in a backup.  If it does, there are 
> some more extensive tests for collisions and on a match the 
> new backup file is replaced by a link to the pooled copy.  
> The file attributes (owner/modes, etc.) are maintained 
> separately in the attrib file in the backup directory since 
> these may be different for different instances of the same 
> content.  This approach works whether the content is 
> duplicated in multiple backup runs on the same machine or the 
> same content is found on many machines.  A side effect of 
> this technique is that the pool and pc directories (and 
> everything below) must always be on the same filesystem.

Many thanks for this explanation.
F.

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
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/