Stephen Joyce <stephen <at> physics.unc.edu> writes: > > Wouldn't it be easier to eliminate the problem? BackupPC is comparing the > files to determine if they're identical (normally using lots of CPU to > uncompress the pooled file, but since you're not using compression, that's > not your issue). > > Why not simply name your database dump differently each time it occurs? My
We may well do that next time we rebuild that server. For now, it is so tightly enmeshed in various scripts that changing it would require taking down some business-critical things for testing so it's not worth the effort at the moment. It's interesting, though, that the BackupPC server -- with slower CPU and slower disk -- appears to checksum the file in a few minutes, while the remote rsync takes hours. I am pretty sure that rsync talking to rsync doesn't behave like this ordinarily and that something about what BackupPC is doing is causing problems. But surely I'm not the only one using BackupPC with rsync with 24GB files changing? That's not all that large of a file size (other examples I can think of include video editing, etc) ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ 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/
