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';
fwiw my soon-to-be-decommissioned prior backuppc server is still backing up
the target server without issue. it's still located where it can reach the
target server directly. it uses:
$Conf{RsyncClientCmd} = 'ssh -xq $host sudo /usr/bin/rsync $argList+';
but while the new backuppc is working fine for servers it can reach
directly, for the double hop it says: "fileListReceive failed"
any ideas?
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
