Rsync between 2 datacenters not working

[Dan Stromberg]

You could try using an automounter, like autofs, in combination with
sshfs.  It'll be slower, possibly a lot slower, but it should be more
reliable over an unreliable connection.

I've been using:
remote -fstype=fuse,allow_other,nodev,noatime,reconnect,ServerAliveInterval=15,ServerAliveCountMax=40,uid=0,gid=0,ro,nodev,noatime
:sshfs\#root at remote.host.com\:/

BTW, I'm not sure it's necessary to escape the #.  I never tried it without.

Also note that it flattens the remote host's mount tree into a single
filesystem - so things like /proc look like they are in the same
filesystem as /.  This can lead to backing up /proc's contents (many
pseudofiles), if you don't exclude it, even if you use rsync's -x
option.

On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync
<rsync at lists.samba.org> wrote:
>
> I still stuck with these errors
>
> packet_write_wait: Connection to 192.168.10.43 port 22: Broken pipe
> rsync: connection unexpectedly closed (534132435 bytes received so far)
> [receiver]
> rsync error: error in rsync protocol data stream (code 12) at io.c(605)
> [receiver=3.0.9]
> rsync: connection unexpectedly closed (27198 bytes received so far)
> [generator]
> rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9]