On 20.03.2017 16:46, Pavel Polacek via Duplicity-talk wrote:
Hello,
I'm using duplicity and I must say, that it's very interesting piece of
software.
I migrated one server from debian to centos 7. Backup time is very long now. It
worked fine on debian.
scp copy from server to server is around 70MB/s
During backup one cpu core is high (from 70 to 100%). On remote side is data
copied around 230kB/s.
Version of duplicity: duplicity-0.7.11-2.el7.x86_64 with default settings
(250MB tar gpg archives).
#duplicity --progress --exclude-filelist filelist_exclude.txt
--full-if-older-than 30D / scp://address@hidden:22
Reading globbing filelist filelist_exclude.txt
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Last full backup is too old, forcing full backup
^[[BReading globbing filelist filelist_exclude.txt
0.0KB 00:00:03 [0.0KB/s] [> ] 0% ETA 3sec
0.0KB 00:00:06 [0.0KB/s] [> ] 0% ETA 6sec
0.0KB 00:00:09 [0.0B/s] [> ] 0% ETA
Stalled!
0.0KB 00:00:12 [0.0B/s] [> ] 0% ETA
Stalled!
0.0KB 00:00:15 [0.0B/s] [> ] 0% ETA
Stalled!
0.0KB 00:00:18 [0.0B/s] [> ] 0% ETA
Stalled!
0.0KB 00:00:21 [0.0B/s] [> ] 0% ETA
Stalled!
0.0KB 00:00:24 [0.0B/s] [> ] 0% ETA
Stalled!
0.0KB 00:00:27 [0.0B/s] [> ] 0% ETA
Stalled!
0.0KB 00:00:30 [0.0B/s] [> ] 0% ETA
Stalled!
Do you see something similar?
default is to use the paramiko+scp:// backend. can you try the pexpect+scp://
backend and see if that makes a difference? ..ede/duply.net
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk