| SliceTheAir wrote: |
|---|
| StephenB wrote: |
|---|
| Maybe try using top with the command line toggle (with the backup job running) so you can see how the backup job command line compares with the terminal session? |
How do I do that?? |
If you enter a "c" when top is running (lower case) it will toggle between showing you the command name and the full command line. It's best if you also make the terminal window full screen before you run top.
| SliceTheAir wrote: |
|---|
| StephenB wrote: |
|---|
| You are not using the rsync over ssh add-on correct? |
No I'm not. What is the "big" advantage? Safety, but why and how. |
Normal rsync is not secure - the data is sent unencrypted. Running over ssh results in the data being encrypted. There is a security downside - exposing ssh potentially allows someone access to the destination machine if they can guess the user credentials. So you'd want a strong passwords (which is a good idea in any case).
| SliceTheAir wrote: |
|---|
Now the first one, incremental with new data gives an error
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Connection timed out (60)
rsync: connection unexpectedly closed (3731 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] |
I'm not certain, but this may be a bug in the rsync server (on the destination machine).
https://bugs.launchpad.net/ubuntu/+sour ... bug/988144
