Craig Barratt wrote: > John writes: > >> I am noticing an issue in our backuppc installation. >> >> Every Monday we have 20-30 hosts (of 84) that were not backed up in >> the prior 24 hours. It seems the /var/log filesystem takes much longer >> on the sunday/monday backups than it takes during the rest of the >> week. >> >> [snip] >> >> I think the problem is that log files are rotated on Sunday AM, so the >> Sunday night/Monday morning backup run has to transfer the entire >> contents of these log files because the names change during the log >> rotation. > > Yes, that makes sense. Unfortunately a renamed file cannot be easily > matched, so it has to be transferred and then matched against the pool. > > (A better approach with log files is to append the date stamp to the > name, rather than an incrementing number.) > > Any chance you have sparse files in /var/log? They can be very large, > and none of the Xfer methods detect sparse files.
Some versions of 64-bit linux will have a sparse /var/log/lastlog that will be 1.2 terabytes if you transfer it the hard way: http://en.wikipedia.org/wiki/Lastlog It might be a good thing to exclude on general principles. -- Les Mikesell [EMAIL PROTECTED] ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ 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/
