Hi Libor!
Thanks for your hint!
In fact using rsync via ssh as workaround *does work for me*, too.
This indeed adds an extra performance penalty for the SSH tunneling, but
in my final setup SSH will be required anyways.
In fact this issue seems to occur mainly with slow rsync servers like
N
I can't believe it -- but I DO fiddle around with _wireshark_ to get my
_backup_ done. Strange age of the 21th century.
Ok - here is what I was able to observe: At first everything seems to be
fine. After handshake the rsyncd is continuously sending every 1.7s
packets to the client which the c
Damn! Just in the moment I clicked send it aborted again.
This is the tail of my rsyncd.log:
2012/10/12 19:36:06 [7325] chunk[261276] offset=34245967872 len=131072
sum1=db0593fa
2012/10/12 19:36:06 [7325] [receiver] _exit_cleanup(code=30, file=io.c,
line=137): entered
2012/10/12 19:36:06 [7325]
Wow: Thanks for your fast responses, Justin and Karl!
Yet the NAS is still located in my home network. So the network
connection shouldn't be the problem.
The pointer to the --inplace argument was really helpful. This is what I
really wanted in this particular use case.
I also tried to enab
Hi list!
I'm trying to use rsync to do a regular remote backup of a 450GB sized
container file located on my squeeze server onto a colocated QNap NAS
device.
Both use rsync 3.0.7. While this setup works for most files, it fails on
this large file (see log below).
I'm already trying to help
