Ben Escoto wrote:
"Carsten Lorenz" [EMAIL PROTECTED]
wrote the following on Fri, 14 Oct 2005 10:03:37 +0200
I started the first backup to an empty directory on a second server.
...
Wiebe Cazemier wrote:
Carsten Lorenz wrote:
I started the first backup to an empty directory on a second server.
I'm wandering about the low speed of ca. 1.6MB/s
Both servers are DL380 with dual PIII 833MHz running debian, python2.3,
librsync 0.9.7-1 and rdiff-backup 1.0.0-0.cvs20050819
dean gaudet [EMAIL PROTECTED]
wrote the following on Fri, 14 Oct 2005 19:58:32 -0700 (PDT)
On Fri, 14 Oct 2005, Carsten Lorenz wrote:
Has anyone hints how to speedup rdiff-backup?
i just had a random idea while reading one of the other threads...
maybe fsync is the culprit for the
I started the first backup to an empty directory on a second server.
I'm wandering about the low speed of ca. 1.6MB/s
Both servers are DL380 with dual PIII 833MHz running debian, python2.3,
librsync 0.9.7-1 and rdiff-backup 1.0.0-0.cvs20050819 (thanks to Dean
Gaudet for the debian package).
They
Carsten Lorenz wrote:
rdiff-backup needs 132s to transfer a 140MB file (1.1MB/s).
While rdiff-backup works on the next file scp transfers the same file in 15s
(9.3MB/s)!
What does that mean? scp = 9.3MB/s rdiff-backup = 1.1MB/s
Since we want to backup one tera-byte of data this would last
Steve Clement wrote:
Carsten Lorenz wrote:
rdiff-backup needs 132s to transfer a 140MB file (1.1MB/s).
While rdiff-backup works on the next file scp transfers the same file in 15s
(9.3MB/s)!
What does that mean? scp = 9.3MB/s rdiff-backup = 1.1MB/s
If i understand, what you mean,
On Fri, 14 Oct 2005, Carsten Lorenz wrote:
Since we want to backup one tera-byte of data this would last more than a
week.
i've never looked closely at why the first backup is so slow -- and i've
heard the report from lots of folks... i tend to use rsync for the initial
backup, and then use
Carsten Lorenz [EMAIL PROTECTED]
wrote the following on Fri, 14 Oct 2005 10:03:37 +0200
I started the first backup to an empty directory on a second server.
...
Everything looks fine:
CPU-usage on the source-server is ca.15% for ssh and ca. 6% for rdiff-backup
CPU-usage on the destination is
