Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I installed BackupPC toda on a server and set it to do a back-up 12 hours ago... while it's been backing up since, it seems very very slow and it's not completed yet. It's just backing up a testserver with a total disk usage of 1.8GB.

What could cause the back-up process to be so slow? rsnapshot always worked wonderfully fast, but I want to improve my back-up solution.

df shows that the size on the back-up disk is actually still increasing.

share|improve this question
    
No experience with the product, but is it possibly hung on an open file? I'd hope not, or I'd say your improvement was a step backwards. –  squillman Jun 20 '11 at 14:46
    
df shows that the size on the back-up disk is actually still increasing. –  ujjain Jun 20 '11 at 15:16
    
And it's not yet to 1.8GB? –  squillman Jun 20 '11 at 16:10
add comment

1 Answer

up vote 1 down vote accepted

What transfer method do you use? Backuppc defaults to rsync, which should be reasonably fast on a LAN connection. So, first of all, I'd take a look at the effective network transfer speed using atop on your backup server. It should give you something far exceeding 20 MBit/s on a normal LAN. If it's slower, check if the network connection is flaky or overloaded.

As a next step, I'd take a look at the load on client and server. Again, using atop, you should easily see if there's a CPU intensive job that shouldn't be there -- if you followed the docs, the rsync process on the client will run at niceness 19, which is the lowest scheduling priority there is, and would be displaced by any "CPU hogs". Another problem might be lack of memory: if the machine's constantly swapping, that would affect disk I/O negatively (since you're talking about a test setup, I'll assume you only use one hard drive).

Oh, and a final thought -- did you remember to exclude stuff like /dev/random from your backup? That would be a file where bytes "trickle" out slowly, and if the process would be looking for an EOF there, it'd have to be lucky :-)

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.