Rather than have backuppc schedule the number of simultaneous backups based on a number of jobs; how about having it schedule based on the current system load? So if the load is >2 for instance, don't start any new backups.
This would alleviate the problems with backups which run forever, trickling in only a little data, but not causing much load on the system and blocking more jobs from being queued. this happens when a backup hangs, or else when you deliberately rate-limit a backup in order to avoid crushing the client machine in question. you'd probably have to put some sort of rate-limit on this, so it didn't suddenly crush the box just because the load went down temporarily. Any thoughts on possible problems with this idea? I usually set my number of simultaneous backups = 2; because otherwise the amount of disk contention slows all the processes down. -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
