|
In case you don't get a quick answer, I'm pretty
sure the answer is: Yes, this is normal.
Personally, I don't "like it", because that is a
lot of overhead, depending upon the directory/backup sizes and the
latency/bandwidth from the client to the backup server (target), but I have
never dived into the source to see where they may have reduced it substantially
and what the trade-offs are to do it. So I "grin and bear
it".
I like duplicity a lot. I consider this just
a small price to pay for the other great work.
-AJ
----- Original Message -----
Sent: Wednesday, February 10, 2010 1:28
PM
Subject: [Duplicity-talk] Is this normal
behavior?
I've been running duplicity from a cron job to back up to a remote server
using ssh. Works fine. Here's one line from my script:
Actually, I have 5 lines, each backing up a different
directory.
It works as expected, but it seems that each command accesses the
server via ssh 11-13 times! And the entire script will access the server
80 or more times each night!
It's not a really big deal, but I'm wondering if this is normal behavior
for duplicity. Does each command do some sort of "checking" of the
destination directory, log out, and log back in over and over again?
Just looking for some explanation for my friend who is hosting this
server.
Thanks!
Todd
_______________________________________________
Duplicity-talk
mailing
list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk
|