I now also added ionice to avoid a lot if io-load on the server being backed up.
My RsyncClientCmd now looks like this:
$sshPath -q -x -l backuppc $host /usr/bin/nice -n 19 /usr/bin/ionice -c2
-n7 /usr/bin/sudo $rsyncPath $argList+
-c2 is the "best effort" class and -n7 is the lowest priority in
"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
I'm using backuppc version 3.1.0-6ubuntu4 on Ubuntu 9.10.
I'm using "fairly recent hardware" (my backup server uses an Intel Atom
330 CPU, a 1.6 GHz dual-core CPU), yet, this effects me. Here's some of
the output of top during a backup:
28539 backuppc 20 0 202m 141m 1368 R 98 4.0 5:26
The workaround described in an above comment constitutes a viable
option. This symptom is not reproducible on fairly recent hardware.
** Changed in: backuppc (Ubuntu)
Status: New => Won't Fix
--
Takes all CPU time
https://bugs.launchpad.net/bugs/67811
You received this bug notification b
I chose a different backup software and don't have backuppc installed at
the moment. Unfortunately, I don't have time to test this anytime soon.
--
Takes all CPU time
https://bugs.launchpad.net/bugs/67811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Thank you for your report. I apologize that no one has gotten back to you
about this yet.
Is this problem still present?
--
Takes all CPU time
https://bugs.launchpad.net/bugs/67811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
