Tino,

Very good explanation.  One minor comment...

> The whole process works roughly like this:
> - backups are done by BackuPC_dump on per-client basis, no explicit
>   pooling involved yet (apart from full backups where existing/unaltered
>   files are linked into the new backup from last full, so link count in
>   the pool increases too)

Actually any new file is linked immediately if it exists in the pool.
Rsync additionally can avoid transferring the file (or transfer just
the changes to file) provided a file with the exact same path exists
in the prior (reference) backup.

> - BackupPC_link traverses completed backups and links new files to the
>   pool (so the new file has link count 2)
> - when a backup starts, old backups get expired and are moved to the
>   trash directory without further processing
> - BackupPC_trashClean simply removes everything in the trash
>   periodically -> link count on some files in the pool decreases
> - BackupPC_nightly skims through the pool and removes files with link
>   count 1 since they are not used by any backup any more

Craig

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
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/