On Tue, Mar 16, 2021 at 8:45 AM <backu...@kosowsky.org> wrote:
> gregrwm wrote at about 19:59:53 -0500 on Monday, March 15, 2021:
> > i'm trying to use a double hop rsync to backup a server that can only be
> > reached indirectly. a simple test of a double hop rsync to the target
> > server seems to work:
> >
> > # sudo -ubackuppc rsync -PHSAXaxe"ssh -xq 192.168.128.11 ssh -xq"
> > --rsync-path=sudo\ /usr/bin/rsync 192.168.1.243:
> /var/log/BackupPC/.bashrc
> > /tmp
> > receiving incremental file list
> > .bashrc
> > 231 100% 225.59kB/s 0:00:00 (xfr#1, to-chk=0/1)
> > 0#
> >
> > which demonstrates that the backuppc keys, sudo settings, and double hop
> > rsync all work.
> >
> > here's my double hop settings:
> > $Conf{RsyncClientCmd} = 'ssh -xq 192.168.128.11 ssh -xq 192.168.1.243
> sudo
> > /usr/bin/rsync $argList+';
> > $Conf{ClientNameAlias} = '192.168.128.11';
>
> Why don't you try using the 'jump' host option on ssh.
> -J 192.168.128.11
>
seems like a really good idea. so i tried:
$Conf{RsyncClientCmd} = 'ssh -xqJ192.168.128.11 sudo /usr/bin/rsync
$argList+';
$Conf{ClientNameAlias} = '192.168.1.243';
and got:
Got remote protocol 1851877475
Fatal error (bad version): channel 0: open failed: connect failed: Name or
service not known
stdio forwarding failed
Can't write 1298 bytes to socket
fileListReceive() failed
if you've any ideas how to tweak that and try again i'm eager,
thank you,
greg
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
