"This symptom is not reproducible on fairly recent hardware." Hmm. That's an interesting statement. First of all, BackupPC does not state that we need "fairly recent hardware" in it's requirements: http://backuppc.sourceforge.net/faq/BackupPC.html#requirements
And I heard PCs from 2006 (when the bug was posted) are still used here or there ;-) And I guess some of them need to be backed up. And even if we have "fairly recent hardware", some users might want to work with the computer that is currently backed up while the backup is running. When you backup a laptop, you might be able to avoid this. Simply run the backup at night. But if you run a server 24/7, then you can't tell your visitors from the other side of the earth not to visit your website at night. So the backup should not affect the load significantly. So of course the backup should run with low priority. And (as Neal wrote), it is easy to achieve this. I added "nice" RsyncClientCmd like this: $sshPath -q -x -l backuppc $host nice -n 19 /usr/bin/sudo $rsyncPath $argList+ Note: Here more things are changed from the default. The username is "backuppc" (not root) and sudo is used to run rsync (with user backuppc being allowed to run rsync in suoders). The adjusted default would look like this: $sshPath -q -x -l root $host nice -n 19 $rsyncPath $argList+ As imho "nice" is pretty standard in unix, I guess it might be a good idea to add this in the default settings. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/67811 Title: Takes all CPU time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/67811/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
