Jim Wilcoxson wrote:
>> What does it use to map the hardlinks internally? Is this
>> likely to remain correct if backuppc rebuilds collision chains in the
>> pool during a copy - or even before the next incremental?
>
> I'm not very familiar with the internals of BackupPC, but if you have
> a set of files that are hard-linked, back them up with HashBackup,
> delete the files, back that up, then recreate the hard-linked files
> and back them up again, it should work even though the new series of
> files will likely have different inodes.
Backuppc finds pool matches with a hash computation and keeps an extra
hardlink with the hash as a filename. There are collisions in this
scheme and as a part of pool maintenance the collision-chain files may
be renamed. If you track the source inode numbers they should stay the
same - but you'll end up with a table of millions to match up.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
