also sprach Mike <ispbuilder AT gmail DOT com> [2012.08.27.1502 +0200]:
> The fix I've used is to --exclude a good chunk of the backup so it does 
> finish in a day, then --exclude a little less the next time it runs, and 
> so forth.

I have used this method, which you and Les suggested. And yes, it
works. However, it's hardly a "fix" or even an acceptable solution
in a large-scale deployment. There is no way I can tell this to
hundreds of users who do occasionally dump larger files to their
home directories.

BackupPC must be able to cope with this, or it must learn.
Otherwise, I am afraid, it is unsuitable.

Do you see a way? How can I force it to use the last partial backup
as a baseline when attempting a new full backup?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"without music, life would be a mistake."
                                                 - friedrich nietzsche
 
spamtraps: madduck.bogus AT madduck DOT net

digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
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/